[Seaside] How is session expiration expected to work considering this?

Mariano Martinez Peck marianopeck at gmail.com
Mon Jul 31 19:49:34 UTC 2017

Hi guys,

I was not yet able to correctly set session expiration timeout for my app.
I was doing something like this:


app := *(WAAdmin register: self asApplicationAt: aSuffix)*
preferenceAt: #sessionClass put: DpWebSession;
preferenceAt: #actionPhaseContinuationClass put:
preferenceAt: #trackingStrategy put:
FaWAQueryFieldAndCookieTrackingStrategy new;

*app configuration at: #maximumRelativeAge put: seconds.*
*app configuration at: #maximumAbsoluteAge put: 0.*

"much more here to continue  customizing the app"


What is the problem? That #register:asApplicationAt: ends up creating the
cache BEFORE I can change the configuration...   so the 'cache' is created
with the default 1800 rather than with what I want.

The workaround is to either do "app cache: app createCache"   or "app
initialize" once I am done with all my configuration... but it looks...


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/seaside/attachments/20170731/e2af3fd7/attachment.html>

More information about the seaside mailing list