Or implement a "remember me" feature in the request cycle. -- Jeremy Thomerson http://www.wickettraining.com
On Fri, Jun 12, 2009 at 2:38 PM, Jeremy Thomerson<jer...@wickettraining.com> wrote: > Just lengthen the session timeout - how to do this depends on your > servlet container. > > -- > Jeremy Thomerson > http://www.wickettraining.com > > > > > On Fri, Jun 12, 2009 at 2:37 PM, Christopher L > Merrill<ch...@webperformance.com> wrote: >> Jeremy Thomerson wrote: >>> >>> the path is stored in the session, so as long as your app server >>> reloads existing sessions on restart, it should (iirc). however, in >>> your dev environment, the app server probably blows away sessions >>> >>> hrmmmm, i just re-read and realized that you said this is for the >>> PageExpired.... which is typically encountered when you lost your >>> session - so this won't work for that. But it will work if I go back >>> twenty pages and click a link - not super helpful. Sorry. >> >> Ahhh...you had me all excited! :> >> >> So maybe my question is really about controlling session duration. >> We don't want our user to be forced to re-authenticate throughout the >> day - so maybe I'm asking the wrong question...Is there another way >> I should be approaching that problem? >> >> >> >> >> -- >> ------------------------------------------------------------------------ - >> Chris Merrill | Web Performance, Inc. >> ch...@webperformance.com | http://webperformance.com >> 919-433-1762 | 919-845-7601 >> >> Website Load Testing and Stress Testing Software & Services >> ------------------------------------------------------------------------ - >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
