Back to Rendra's problem with session-timeout. I am not 100% sure but
my experience is that you have no possibility to find out that session
is about to timeout and modify its timeout behavior. And there is also
problem that servlets are request-response based, so you cannot send
anything to the user without previous request.
If you want to redirect the user to "previous" page in case of s/he
had active session and it's timeouted and then s/he sends next request I
thing the only possibility is to use cookies, store there some
identifier and on the servlet side store the same identifier with URL of
"previous" page to the DB. Then, when new session is created, check if
the user has apropriate cookie and if yes, redirect him/her to the URL
from the DB.
J.Ch.
--
Ing. Jozef Chocholacek Qbizm Technologies, Inc.
Chief Project Analyst ... the art of internet.
________________________________________________________________
Kralovopolska 139 tel: +420 5 4124 2414
601 12 Brno, CZ http://www.qbizm.com fax: +420 5 4121 2696
___________________________________________________________________________
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
