[Seaside-dev] Issue 96 in seaside: some fancier methods built in for how sessions expire

[codesite-noreply at google.com]

Issue 96: some fancier methods built in for how sessions expire
http://code.google.com/p/seaside/issues/detail?id=96

Comment #3 by jfitzell:
I committed some work to pull expiry out into pluggable policy classes.  
Comments on
the dev list appreciated...

Name: Seaside-Core-jf.expirypolicy.1
Author: jf
Time: 17 September 2008, 4:35:48 pm
UUID: 7c944d9c-8681-cb45-b1e4-66c8a18d38f6
Ancestors: Seaside-Core-jf.239

Expirment pulling session expiry behaviour (actually expiring handler  
expiry) into
its own set of expiry policy classes.


Name: Seaside-Session-jf.expirypolicy.1
Author: jf
Time: 17 September 2008, 4:37:26 pm
UUID: 77c0b7ef-77ec-9347-a1c6-a99f8bc1cd89
Ancestors: Seaside-Session-pmm.12

The introduction of expiry policies in Seaside-Core-jf.expirypolicy.1  
allows us to
remove #incomingRequest: from WASession and just use #responseForContext:

Not sure how best (or whether) to mark the old method as deprecated...



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