[Seaside-dev] Issue 208 in seaside: WASessionContinuation uses WARequest and WARequestContext

[codesite-noreply at google.com]

Issue 208: WASessionContinuation uses WARequest and WARequestContext
http://code.google.com/p/seaside/issues/detail?id=208

Comment #4 by jfitzell:
Name: Seaside-RenderLoop-jf.15
Author: jf
Time: 19 October 2008, 1:12:17 pm
UUID: c249c4cc-6281-6941-9995-85c8318b26c6
Ancestors: Seaside-RenderLoop-lr.14

Name: Seaside-Session-jf.31
Author: jf
Time: 19 October 2008, 1:08:56 pm
UUID: d1253462-5220-ae47-9a87-262747b8c19e
Ancestors: Seaside-Session-jf.30

http://code.google.com/p/seaside/issues/detail?id=208

Change session continuations and sessions request handling methods so they  
use
#currentRequest (most cases) or at least get passed a RequestContext  
instead of of a
Request.

Specifically:

Change WAMain>>start: to #start
Change WASession>>start: to #start
Change WASession>>unknownRequest: to #unknownRequest
Move WASession>>performRequest: code into #responseForContext:
Change WASessionContinuation>>handleRequest: to #handleRequest
Change WASessionContinuation>>value: to #value


Issue attribute updates:
	Status: Fixed

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings