Alright, I figured out a way of detecting session timeout and performing
cleanup after its death.
example:
1. user logs in (creates a session)
2. user modifies some tables in the DB
3. user closes the browser, leaves it unattended, logs out, disconnects from
the internet, etc.. (session timesout)
4. after session's timeout, it resets all of the previously modified tables.
This can be done using HttpSessionBindingEvent and
HttpSessionBindingListener.
basically, have a "clean-up" object implement HttpSessionBindingListener,
and then during the creation of the session, just add this object to the
session " session.setAttribute("OBJECT",new CleanUp()) "
After the session expires/timesout/invalidates, it will send out an event to
your Cleanup object where you can do all sorts of neat things.
_I
p.s.
I noticed the following trend on this mailing list... If you want your
question to be answered ASAP, you better be asking about something that's
totally not related to JSP... even though you will get a couple of lines of
"this is a JSP list", chances are that you'll at least get an answer
(usually more than 1).. Next time if I have any kind of questions regarding
JSP, I'll be visiting mySQL, Jakarta, Apache, Swing/AWT lists.. if those
groups exhibit similar trends, I'll be getting answers in no time :)
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
