[Seaside-dev] Issue 285 in seaside: respondAndContinue: does not use a SessionCallback

[codesite-noreply at google.com]

Status: Accepted
Owner: ----
Labels: Type-Defect Priority-Medium Version-Seaside2.9 Version-Seaside2.8

New issue 285 by jfitzell: respondAndContinue: does not use a  
SessionCallback
http://code.google.com/p/seaside/issues/detail?id=285

WARequestContext>>respondAndContinue: does not use a session continuation.
Instead it registers a first-class continuation with the Session. This
means that state is not restored when the continuation is activated.

It works fine as long as no other continuations are activated in the  
meantime.

This method was called WASession>>respond: in Seaside 2.8.x

This is only used for testing session cookies at the moment within the
framework but may be used by users to set cookies or otherwise. It is also
used to implement #redirect, which can  be used to force a change of URL.

It should be possible to fix this but it suffers the same problem as
#inNewRenderLoopCall: in that I currently see no way of getting at the
current root component.

--
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