[Seaside-dev] Issue 19 in seaside: Behaviour of #initialRequest:/#updateUrl differs when using session cookies.

[codesite-noreply at google.com]

Issue 19: Behaviour of #initialRequest:/#updateUrl differs when using  
session cookies.
http://code.google.com/p/seaside/issues/detail?id=19

Comment #5 by jfitzell:
Ok, I see the specific problem:

WARequestContext>>respondAndContinue: can't use the #actionUrl that was  
passed into
the request context by the session continuations because it needs a link to  
a
different continuation. As a result, it calls  
WASession>>actionUrlForContinuation: to
get a new URL but the components and session have not had a chance to  
update that URL
so we lose the extra parameters.

#respondAndContinue: is used by #testSessionCookie and  
#redirectWithCookie:, among
others.

So what's the right fix? I'm not sure. It might be better to have the  
session call
#updateUrl: on its own root object in #actionUrlForKey: except that the  
root object
is not currently stored on the session. It might be best to look at this  
again after
the painter refactoring is merged into the trunk.


Issue attribute updates:
	Owner: ---

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