[Seaside] session expire time in seaside 3.0

Julian Fitzell jfitzell at gmail.com
Sun Jan 3 10:20:57 UTC 2010

On Sat, Jan 2, 2010 at 5:58 PM, Sean Allen <sean at monkeysnatchbanana.com> wrote:
> On Sat, Jan 2, 2010 at 5:25 PM, Philippe Marschall
> <philippe.marschall at gmail.com> wrote:
>> 2010/1/2 Sean Allen <sean at monkeysnatchbanana.com>:
>>> how do you dynamically set the session expire time in seaside 3?
>> You mean on a specific session instance? You don't, Julian broke it
>> ;-) but patches are welcome :-)


> no i mean how do i set the session timeout per application.
> i thought i knew how to do for 3.0 but turns out i knew for 2.8
> and i spent an hour trying to figure it out before finally
> deciding asking here was a much smarter way to find out.
> dynamically might not have been the best word.
> like the old
> application preferencesAt: #sessionExpirySeconds put: 3600

Philippe's right... it's a bit ugly at the moment. What you want is
inherited from WARegistry.

Something like:

application cache expiryPolicy configuration at: #cacheTimeout put: 600


More information about the seaside mailing list