I don't know exactly how you have your app organized, but at least
from the Seaside point of view, expired Sessions are swept "lazily",
meaning that there is no background process checking whether a Session
is expired, but on each access to the cache it will call
#sweepIncrementally.
If it works for you, you can define a maximum age of the session,
meaning that it will expire by being old (and not necessarily idle).
But if you only have one session, and nothing starts a new session,
then it will never reap the old session.
An workaround is to have a JS background loop in the browser (using
setInterval() o recursively via setTimeout()) that "pings" the server
with an empty callback, on each request this will check whether the
session key belongs to an active session, and it will expire the
session if it exceeds the maximum age.
On the server side you could have a forked process that loops and
waits on a Delay, and manually calls the sweepIncrementally, but
you'll have to fiddle with the internals of your WAApplication, get
the cache, etc.
Regards!
Esteban A. Maringolo
> --
> You received this message because you are subscribed to the Google Groups "VAST Community Forum" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
va-smalltalk...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/va-smalltalk/35aa8a90-4b4a-4db4-be28-d6fb12ca30dcn%40googlegroups.com.