[Seaside] purge expired sessions
Julian Fitzell
jfitzell at gmail.com
Sun Feb 22 17:53:21 UTC 2009
WARegistry>>unregisterExpiredHandlers ?
It should be called periodically as sessions are created (whenever
#shouldCollectHandlers returns true).
So expired sessions will not be garbage collected immediately but they
should eventually be released.
Julian
On Sun, Feb 22, 2009 at 6:28 PM, Sebastian Sastre <ssastre at seaswork.com> wrote:
> Hi there,
> I'm on seaside 2.8 and I'm seeing expired sessions not being collected. Of
> course #clearHandlers helps but that isn't helpful in a production serving image
> because it will force expiration of sessions of users navigating the app.
>
> I wanted to know if you do (or why you don't) make a method to call from time
> that will remove from the WARegistry handlers dictionary the expired sessions.
>
> Or maybe better, why not to remove sessions from there immediately after they
> expire so unuseful things can be collected ASAP.
>
> thanks,
>
> sebastian
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
More information about the seaside
mailing list