1. I would have preferred to do it by keeping the info that a used is
currently logged in, in a database table rather than GlobalSessionObjects.
GSOs are notorious for affecting performance since only one person in the
world can read or write to it at a time - a single and narrow  bottleneck.

2. You can invoke a JavaScript function onUnload() of the document - (an
event on the BODY if I remember correctly or else the FORM) - to open a new
window and call a logout ND page, which in addition to doing the logout
processing will tell the user "I have logged you out for you".

3. The other thing to be taken care of is the onSessionExpiring event. (The
user may not close the browser, he may just walk away for a coffee and meet
somebody on the way!). If you keep the useid as a UserSessionObject you
should be able to handle this too.

Good luck.

Aby

-----Original Message-----
From: Amit [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 08, 1999 8:08 AM
To: [EMAIL PROTECTED]
Subject: [ND] LOGOUT!!



Hi,
I need to keep track that only one user can log into the system at any given
time 
using one particular id. I keep track of that in the global session object.
Also when the
user logs out I remove the info from the global session. But the problem is
if the user 
exits from the browser without logging off. In that case I'm unable to
remove the info 
from the global session. Is there a way to force the logout event to trigger
when the 
window is closed?I'd appreciate if any one has any thoughts on this. 
Thanks.
Amit.
_________________________________________________________________________

For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html

For dire need help, email: [EMAIL PROTECTED]
_________________________________________________________________________

For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html

For dire need help, email: [EMAIL PROTECTED]

Reply via email to