Ok, but what happens to their form bean? It would be gone, and thus their performance evaluation data would be gone. No?
Craig. >From: "Jon.Ridgway" <[EMAIL PROTECTED]> >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> >Subject: RE: What happens when our session expires? >Date: Mon, 28 Jan 2002 10:12:13 -0000 > >Hi Graig, > >Most Servers (Web & J2EE) have a session timeout setting. If used in >conjunction with form based (container managed) authorization, the >container >will invalidate the session for you and pass control automatically to your >login screen once their session is invalidated. > >Jon. > >-----Original Message----- >From: Craig Tataryn [mailto:[EMAIL PROTECTED]] >Sent: 28 January 2002 07:19 >To: [EMAIL PROTECTED] >Subject: RE: What happens when our session expires? > >Thanks! Would there be a way we could manually end a session (i.e. at >logoff?)? > >I would say that at some point (perhaps 24 hours) we would want the session >to expire, I imagine if we never expired sessions we would get into some >really bad performance issues... > >Craig. > > > >From: "Jason Chaffee" <[EMAIL PROTECTED]> > >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > >To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > >Subject: RE: What happens when our session expires? > >Date: Sun, 27 Jan 2002 22:59:04 -0800 > > > >One approach would be to not let the session timeout. The 2.3 servlet > >spec. allows you to set the timeout to -1, which means the session will > >never expire. > > > > -----Original Message----- > > From: Craig Tataryn > > Sent: Sun 1/27/2002 10:37 PM > > To: [EMAIL PROTECTED] > > Cc: > > Subject: What happens when our session expires? > > > > > > > > Hi there, you probably have heard this question a million times > >before, but > > I couldn't really find anything in the archive which answered > >it. So here > > it goes: > > > > We have an application for which we would like to use struts. > >This > > aplication allows users to enter performance evaluation > >information on > > employees in the firm. > > > > I would like to know this: The user starts a performance > >evaluation, and > > half way through decides to go grab a bite to eat, comes back > >and finshes > > the evaluation, when he/she hits the "save evaluation button" > >their session > > is going to be kaput. Let's assume that the evaluation is a > >wizard type > > application and relied heavily on an ActionForm class to store > >the > > information entered on each page. > > > > How do you overcome this problem? Make sure to store all their > >previously > > entered performance evaluation data in a hidden field on the > >client side? > > > > Any help would be greatly appreciated. > > > > </tataryn:craig> > > > > Craig W. Tataryn > > Programmer/Analyst > > Compuware > > > > > >_________________________________________________________________ > > Get your FREE download of MSN Explorer at > >http://explorer.msn.com/intl.asp. > > > > > > -- > > To unsubscribe, e-mail: > ><mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > ><mailto:[EMAIL PROTECTED]> > > > > > > > ><< winmail.dat >> > >-- > >To unsubscribe, e-mail: > ><mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: > ><mailto:[EMAIL PROTECTED]> > > >Craig W. Tataryn >Programmer/Analyst >Compuware > >_________________________________________________________________ >MSN Photos is the easiest way to share and print your photos: >http://photos.msn.com/support/worldwide.aspx > > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > Craig W. Tataryn Programmer/Analyst Compuware _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
