This thread has dragged on for rather long.
Is it clear that:
You *cannot* find out when a browser is closed, or (more exactly) when the user has
gone away and isn't coming back.
There are a variety of hacks that *might* work *sometimes*, but there is nothing
reliable enough to count on.
You *must* design assuming that your only hint is the passage of time. You could act
when the session times out. You could act
after a certain number of hours, days, or weeks (as makes sense for your application).
Once you have built and tested your application on this basis, then and only then you
might consider incorporating some of the cute
little tricks discussed on this thread.
You might be able to squeeze out a little optimization by getting back *hints* from
the browser. If so then fine, but don't count
on this in your design.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
