Re: Sessions
Re: Sessions
- Subject: Re: Sessions
- From: Mark Morris <email@hidden>
- Date: Tue, 31 Jan 2006 13:25:10 -0600
Norberto,
I posted this idea in response to another question not long ago, and
it still has the same caveat: I've never tried it. However, if you
register for WOSession's SessionDidTimeOutNotification, serialize the
session to persistent store (like a database), then override
WOApplication's handleSessionRestorationErrorInContext, it seems like
you could restore their session right where it left off. (Perhaps
you'd need to maintain some extra state information, such as the
current page name, so the restoration would be as smooth as
possible.) That way, you could set the timeout to something
reasonable, say 30-90 minutes, and avoid the problem with graceful
shutdowns, etc., but to the user the only effect would be it might
take a tad longer to bring up the first page when they've been off
the app for awhile.
Regards,
Mark
On Jan 31, 2006, at 3:20 AM, Alexander Spohr wrote:
WOSession.setTimeOut(0.0);
but you are not able to do a clean app shut-down after the first
session is alive. don't do it.
atze
Am 30.01.2006 um 21:59 schrieb Norberto Menendez:
How is it that you establish sessions that don't time out in WO
(for an application with a small number of users < 50) ?
Are there any suggested strategies ?
Thanks
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40onpointsoftware.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
| References: | |
| | >Sessions (From: Norberto Menendez <email@hidden>) |
| | >Re: Sessions (From: Alexander Spohr <email@hidden>) |