[Seaside-dev] Issue 213 in seaside: session should not register itself in the application

[codesite-noreply at google.com]

Issue 213: session should not register itself in the application
http://code.google.com/p/seaside/issues/detail?id=213

Comment #1 by jfitzell:
Name: Seaside-Tests-Functional-jf.16
Author: jf
Time: 27 October 2008, 5:45:21 pm
UUID: 76afe0bf-32e8-684a-aa40-b94623a07d9d
Ancestors: Seaside-Tests-Functional-pmm.15

http://code.google.com/p/seaside/issues/detail?id=213
It was really annoying to have the Session automatically register itself in  
the
Application. The caused weirdness when unregistering a session - the render  
phase
would then cause the session to re-register itself under a new key.

To fix this, WAApplication now registers the session when it is created and  
the
session should not re-register itself.

Added #keyFor:ifAbsent: and #urlFor:ifAbsent: as well as #keyFor: and  
#urlFor: which
signal a WAUnregisteredHandlerError if the handler is not found. Change  
senders of
#urlForRequestHandler:addHandlerField: and #ensureKeyForHandler: to use  
these new
methods. The RenderLoopContinuations now catch this error and redirect to a  
new
session. If you want to redirect somewhere else, you should call
WARequestContext>>redirectTo: after unregistering the session.

Also rename several methods on WARegistry to get a more consistent  
interface, both
internally and with WADispatcher) and deprecate the old versions (plus  
changed senders).


http://www.squeaksource.com/Seaside29/Seaside-Tests-Functional-jf.16.mcz
Name: Seaside-Development-jf.31
Author: jf
Time: 27 October 2008, 5:45:28 pm
UUID: 50f5ba3a-b2d2-d14e-9edc-7832bfdb7546
Ancestors: Seaside-Development-jf.30


http://www.squeaksource.com/Seaside29/Seaside-Development-jf.31.mcz
Name: Seaside-Tests-Core-jf.18
Author: jf
Time: 27 October 2008, 5:45:34 pm
UUID: 00619845-bea6-7a45-bdd1-b04af72d3c24
Ancestors: Seaside-Tests-Core-lr.17


http://www.squeaksource.com/Seaside29/Seaside-Tests-Core-jf.18.mcz
Name: Seaside-RenderLoop-jf.20
Author: jf
Time: 27 October 2008, 5:45:39 pm
UUID: fa133e7f-fa04-094f-90fe-38fa600b747d
Ancestors: Seaside-RenderLoop-lr.19


http://www.squeaksource.com/Seaside29/Seaside-RenderLoop-jf.20.mcz
Name: Seaside-Tests-Development-jf.15
Author: jf
Time: 27 October 2008, 5:45:44 pm
UUID: 7dea5c32-032b-d442-8e56-9c8ac4015e68
Ancestors: Seaside-Tests-Development-jf.14


http://www.squeaksource.com/Seaside29/Seaside-Tests-Development-jf.15.mcz
Name: Seaside-Core-jf.301
Author: jf
Time: 27 October 2008, 5:45:47 pm
UUID: cb02ee70-2c74-344a-b6bb-40bd58329104
Ancestors: Seaside-Core-jf.300


http://www.squeaksource.com/Seaside29/Seaside-Core-jf.301.mcz
Name: Seaside-Environment-jf.24
Author: jf
Time: 27 October 2008, 5:46 pm
UUID: a316392a-6115-bd40-9460-6421b3b6ace6
Ancestors: Seaside-Environment-jf.23


http://www.squeaksource.com/Seaside29/Seaside-Environment-jf.24.mcz
Name: Seaside-Session-jf.39
Author: jf
Time: 27 October 2008, 5:46:04 pm
UUID: ee93af56-d1fa-954d-bb87-1cdbe7fdb3d0
Ancestors: Seaside-Session-lr.38

http://www.squeaksource.com/Seaside29/Seaside-Session-jf.39.mcz


Issue attribute updates:
	Status: Fixed
	Owner: jfitzell

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