That will only work if the user hasn't moved off the current page since they
left your server. If they just went on to another site, the refresh is
lost. I'm not sure how useful any of this is. If the user isn't coming
back to the site, they definately don't want to know that their session
timed out, if they are, they'll be notified that the session timed out and
asked to re-log in. Seems to me that the notification is just an annoyance.
(*Chris*)
----- Original Message -----
From: Charles Forsythe <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 26, 1999 2:06 PM
Subject: Re: window alert when session has timed out or other scheme.
> Chris Pratt wrote:
> > Since the reason that a session times out is that there
> > has not been a connection between the browser and server for
> > a specific amount of time (usually 30 minutes), it would be
> > impossible for the server to notify the client of that event.
>
> You could force a connection by embedding a REFRESH directive in your
headers,
> set to 32 minutes (X + 2 minutes, where X is the timeout). That way, just
> after the session expired on the server, the browser would attempt a page
> reload. If the person had left an application page sitting open, then it
could
> do something interactive, like send them to a login screen to
re-authenticate.
> If the user had closed his or her browser, or left the site, then the
session
> would quietly expire on the server.
>
> > ----- Original Message -----
> > From: Ssemwogerere, Joseph <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, August 26, 1999 6:42 AM
> > Subject: window alert when session has timed out or other scheme.
> >
> > > Is there a way to send a JavaScript alert to the screen when the
session
> > has
> > > timed out?
> > >
> > > If the user is on a particular page of the application, they walk away
> > from
> > > their computer, the session times out, when they come back there is
this
> > > little alert window telling them what happened, they click on it to be
> > taken
> > > to the welcome screen where they create a new session and login again.
> > >
> > > I am using JRun 2.3, IIS, Win NT,jsdk 2.1, jdk1.2.
> > >
> > > If you know of a better scheme to handle session time out, that would
be
> > > helpful.
> > >
> > > Joe S.
> > >
> > >
> >
___________________________________________________________________________
> > > 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
>
>
___________________________________________________________________________
> 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
