Bo Xu wrote:
[EMAIL PROTECTED] wrote:
When a Tomcat session times out does it send you to a preset error page?
What is the mechanism there?
What is the best way to handle timed out users?
Hi :-) I suggest you make a object witch implements
When a Tomcat session times out does it send you to a preset
error page?
No. not unless you throw an exception due to dependence on something
from session. You could develop an entire webapp without ever using
the session and despite the fact you never use it it will still be
instantiated.
Title: RE: session timeout handling
Timeout will not send anyone anywhere. When the session expires it cleans up all the objects in the session's attributes. If the objects are of type HttpSessionBindingListener then an event is thrown against them.
The best way to handle timed out users
[EMAIL PROTECTED] wrote:
When a Tomcat session times out does it send you to a preset error page?
What is the mechanism there?
What is the best way to handle timed out users?
Hi :-) I suggest you make a object witch implements
javax.servlet.http.HttpSessionBindingListener, and put object
We carry a userid and a shopping cart in the session thu out the app.
If the user goes to lunch and comes back, we would like to give them sort of
friendly error if their session times out.
At 04:19 PM 6/22/2001 -0400, you wrote:
When a Tomcat session times out does it send you to a preset
Title: RE: session timeout handling
configure something on the page sent to the client which times out after the length of time that your session objects timeout at Something like ..
meta http-equiv=Refresh content=lengthOfTimeInSeconds URL=sorryYouTimedOut.html
-Original Message
We carry a userid and a shopping cart in the session thu out the app.
If the user goes to lunch and comes back, we would like to
give them sort of
friendly error if their session times out.
Allowing the garbage collector(unless you are REALLY nitpicky about
knowing that errant Objects are