How is session expiration expected to work considering this?
Mariano Martinez Peck <[email protected]>
| Newsgroups | gmane.comp.lang.smalltalk.squeak.seaside |
|---|---|
| Message-ID | <CAA+-=mVAd8eATx2V1o=pM8OVuBUrVaOiqg7-9TRzEBFPxZgyDg@mail.gmail.com> |
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: FaCallbackProcessingActionContinuation; preferenceAt: #trackingStrategy put: FaWAQueryFieldAndCookieTrackingStrategy new; yourself. *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... weird... Thoughts? -- Mariano http://marianopeck.wordpress.com _______________________________________________ seaside mailing list [email protected] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside