[Seaside] How to define the duration of my sessions

Johan Brichau johan at inceptive.be
Fri Jan 20 10:38:39 UTC 2017

Hi Sabine,

The caching mechanism changed in Seaside 3.2 (this change was not so well documented).
You can configure as follows: ).

	app configuration at: #maximumAbsoluteAge put: 300

See WACacheConfiguration and the Seaside config page of the app for more info on available parameters.

Seaside invokes #unregistered on a session instance when the session is closed.
Override it with your implementation and it should work fine.

Let me know if you have any issues.


> On 20 Jan 2017, at 10:31, Sabine Manaa <manaa.sabine at gmail.com> wrote:
> Hi,
> how can I define the duration of my sessions? 
>>> application cache expiryPolicy configuration at: #cacheTimeout put: 120.
> does not work any longer (no implementor of #expiryPolicy)
> In the comment of  WASession there is the text "If the session has not been
> used for #defaultTimeoutSeconds, it is garbage collected by the system. "
> but there is no implementor of #defaultTimeoutSeconds.
> And 2nd question, is it possible to define a certain task to do from my
> session instance if the session is unregistered because of duration? (e.g.
> write sth in a log file)
> (From the class comment also: WARegistry clearAllHandlers. does not exist
> any more)
> Regards 
> Sabine
> --
> View this message in context: http://forum.world.st/How-to-define-the-duration-of-my-sessions-tp4930014.html
> Sent from the Seaside General mailing list archive at Nabble.com.
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list