Another more complicated but cool ;-) approach would be to register
for WOSession's SessionDidTimeOutNotification, serialize the session
to persistent store (like a database), then override WOApplication's
handleSessionRestorationErrorInContext to reload the saved session.
You'd still have the session in-memory unless it times out, then
you'd have the ability to reload. You could still decide the session
was too old, if you wanted.
Never tried it myself, but seems like it could be made to work.
Good luck!
Regards,
Mark
On Jan 22, 2006, at 9:38 PM, [EMAIL PROTECTED] wrote:
Hello Norberto;
One way to do this is to add some code to your WO page which causes
a java timer to periodically fire at about half the session
timeout. This javascript should invoke a URL with the wosid from a
direct action. This has the end effect of keeping the session
alive as long as the page is open.
cheers.
I want to build an application where the users should not "time
out"; ideally, they log in, and don't log out until the end of the
day. The application is for a small number of users (<50)
submitting data.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/markm%
40onpointsoftware.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
