Yes, this could work. However, you can never get ALL sessions. Depending how the client process was terminated, the onClose trigger may or may not be received. With CLIENT/SERVER you will never be able to get all cases. Therefore, setting a reasonable session timeout, you can guarantee that your container's GC will remove the sessions.
-----Original Message----- From: David Kerber [mailto:[EMAIL PROTECTED] Sent: Thursday, March 30, 2006 9:48 AM To: Tomcat Users List Subject: Re: Managing sessions - Object destruction I don't know javascript hardly at all, but would it work to write a little script and use an onClose event to trigger a logout request? Victor Hugo Germano wrote: > it should be good for me... > > ty for the explain peter... > :-) > > > Peter Crowther escreveu: > >>> From: Victor Hugo Germano [mailto:[EMAIL PROTECTED] The problems >>> is, when do i have to kill the session?? Even when the browser is >>> closed, the session continues at the memory... >>> >> >> >> Remember that HTTP is a stateless protocol. Tomcat does not (and >> cannot) know that the browser has been closed. All it knows is when it >> last saw a request. After some time (which varies between >> applications), a Web server may make the assumption that the session is >> unlikely to be used again and may tear it down. >> >> Are you expecting a session to end at the instant a user closes their >> browser? >> >> - Peter > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
