[Seaside-dev] expiry policies

[Dale Henrichs]

Julian Fitzell wrote:

>Comments please... :)
>
>
>
>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...
>_______________________________________________
>seaside-dev mailing list
>seaside-dev at lists.squeakfoundation.org
>http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>  
>
I haven't looked at the code, but I like this idea ... session 
expiration is another area where I override behavior. I'd also be 
inclined to make a policy (or include in the expiration policy) the 
algorithm for expiring requests as well (I am reading code and don't 
have things loaded), since the two are related.

Dale