Thanx Nic,
I thought this was a good way to handle it.
I was just looking for some confirmation, I'm kind of a needy person that
way. :)
-Tim
-----Original Message-----
From: Nic Ferrier [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 28, 2002 11:13 AM
To: [EMAIL PROTECTED]
Subject: Re: Session Timeouts
"Chen, Gin" <[EMAIL PROTECTED]> writes:
> Hi all,
> I have an application that I set the session timeout for. Well,
true
> to form, after the timeout period passes, any requests to objects within
the
> old session will result in nullpointerexceptions as that object no longer
> exists. So now I want to handle timeouts more gracefully (give page
> notifying that the timeout has occured blah blah blah).
> My question is this, what is the standard way of doing this?
> Currently, I'm using request.getSession( false ) and checking to see if it
> returns null to me. Is that a good way to handle this? Or should I use a
> check of the create time and/or getMaxInactiveInterval with
> getLastAccessedTime?
You should use a check for null on request.getSession(false) because
timeout is not the only thing that could cause a session to be
destroyed.
Nic
___________________________________________________________________________
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
___________________________________________________________________________
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
