[Seaside-dev] Issue 304 in seaside: caching session cookie state

[codesite-noreply at google.com]

Updates:
	Status: Fixed

Comment #5 on issue 304 by jfitzell: caching session cookie state
http://code.google.com/p/seaside/issues/detail?id=304

(I created Issue 325 to deal with the feature request discussed in Comment  
4)


This came out of and fixes  
http://code.google.com/p/seaside/issues/detail?id=304

Move cookie handling behaviour from Application/Session to Registry  
(including full
unit tests!).

Also make WARegistry non-abstract so it can be used directly in cases where  
you want
to store a dynamic collection of handlers (it will return a 404 in response  
to a
default request with no key).

You will need to clear your configuration cache and reload applications  
after loading
these versions.

Name: Seaside-Core-jf.430
Author: jf
Time: 30 January 2009, 4:19:14 pm
UUID: 5950d50f-023e-4616-8c3f-e53591ab7c3f
Ancestors: Seaside-Core-jf.429

http://www.squeaksource.com/Seaside29/Seaside-Core-jf.430.mcz
Name: Seaside-Session-jf.90
Author: jf
Time: 30 January 2009, 4:19:24 pm
UUID: ed0082b9-7dec-44b8-a5cb-abebd106db6c
Ancestors: Seaside-Session-jf.89

http://www.squeaksource.com/Seaside29/Seaside-Session-jf.90.mcz
Name: Seaside-Tests-Core-jf.72
Author: jf
Time: 30 January 2009, 4:19:29 pm
UUID: 2ed82b98-9278-4153-b075-d1990c2b6eda
Ancestors: Seaside-Tests-Core-jok.71

http://www.squeaksource.com/Seaside29/Seaside-Tests-Core-jf.72.mcz
Name: Seaside-Tests-Session-jf.15
Author: jf
Time: 30 January 2009, 4:19:34 pm
UUID: 1aa69dc6-c634-45ec-9796-c5458885da2e
Ancestors: Seaside-Tests-Session-lr.14

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

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