2005/9/5, Adam Hardy <[EMAIL PROTECTED]>: > Fourthly I think the work involved in making something track all > sessions like this and then inactivate any that stop would be > considerable. At least I can't think of a suitable algorithm off the top > of my head.
I had the same problem: avoiding duplicate user login and at the same time giving the user the possibility to log again in case of browser/network failure without waiting cache/session timeout. I solved redirecting the user to a new login page, if she tries to relogin while a session is still alive. So it's up user responsability deciding to force out the old session. She should know if he's kicking out his boss ;) -- TREMALNAIK --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
