On Sat, Jan 2, 2010 at 5:58 PM, Sean Allen <
[hidden email]> wrote:
> On Sat, Jan 2, 2010 at 5:25 PM, Philippe Marschall
> <
[hidden email]> wrote:
>> 2010/1/2 Sean Allen <
[hidden email]>:
>>> 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 :-)
:P
> 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
Julian
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Locked
