Me too. I alway try to avoid javascript. I have one workaround to the problem that keep me from having a headache with the browser incompatibilities. Since I already have a table in the database that deal with the session number, timestamp and user id. All I have to do is to detect the duplicate user id and check to see if if user is online for no more than 15 minutes by checking the timestamp. If more than 15 minutes then I deleted the existing session id then delete the duplicate user. When all goes well, then I create a new session id and insert it into the database along with the user id and a timestamp. And I do the manual clean up of the leftover session in the /tmp directory every few weeks. Not what I would like to have but there's nothing I can do about browser incompatibilities and javascript issues. If we're lucky, this would take 20 years or more for the problem to be fixed.
"Tamas Arpad" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... On Monday 13 January 2003 18:09, Scott Fletcher wrote: > It's no problem. We're all very interesting in finding out what can work. > > Maybe I can help with one of this problem. The Gecko browser does have the > option of blocking the opening of hte unrequest window which is maybe why > yours doesn't work in Mozilla. Just wondeirng... No, the setting called "Open unrequested windows" is turned on in my browser (Mozilla 1.0.1), and all other settings on that page are also turned on, so I don't know why window.open call doesn't work in onunload event handler. By the way it's not a problem for me :)) I don't know if it works for the original poster. I try to always avoid using javascript, I think the session expiration is still a better way to force logging out a visitor who forgot to click on the logout button. Arpi -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
