Re: How does WO enforce serial request processing per session?
Re: How does WO enforce serial request processing per session?
- Subject: Re: How does WO enforce serial request processing per session?
- From: shaun <email@hidden>
- Date: Wed, 29 Aug 2007 12:31:35 +0930
Peter Vandoros wrote:
We have a situation where we Single Sign On with a 3rd party system. When the
user SSO's into our system, we need to keep their session alive in that 3rd
party system for when the user re-enters that system. We do this by having a set
of TimerTask's firing every X minutes. The idea is that if we detect that the
user's session in the 3rd party system is no longer valid, we have to kick the
user off our session. Essentially, logging the user out of our system.
In this case, we need access to our WOSession in order to log the user out.
How about something along the lines of:
Every n minutes check the 3rd party system for session validity
if 3rd party session is invalid then
put sessionId in application.sessionsToTerminate.
end if
When WOApp session.awake is invoked
if sessionId is in application.sessionsToTerminate
session.terminate
application.sessionsToTerminate.remove(sessionId)
end if
cheers,
- shaun
_______________________________________________
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