-- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. http://www.edgetechservices.net/ 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMAIL PROTECTED]
----- Original Message ----- From: "Aladin Alaily" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <user@struts.apache.org>
Sent: Thursday, May 12, 2005 11:12 AM
Subject: Re: Best practice for redirecting on session timeout?
Hi
Umm..ya...that's why I explicity said "preferrably via an include or let a1) Maintainability: if you want to change the timeout to 30 minutes (and you have 50 jsp pages), then you have to make the change 50 times.
filter do it for you".
Missed the filter part :)
2) Business Logic: This approach will never prevent you Action from executing. Since you have to go through an action to reach the jsp page, when the *page* reloads, you are actually reloading the action first.You must be confused here. The refresh happens ON the client after 20 minutes of inactivity. "Inactivity" being defined as "the browser has no interaction with the server".
Confused? Maybe... but what if the page is not cached on the client-side. Where is the browser going to get it from? ;)
After rereading the original post, it seems that I misunderstood the
original question. My proposed solution assumes you've already dealt with
handling the expired session, so for all intents and purposes, we actually
agree (in a 1/42 kind of way ;)
At least we agree on something :)
Aladin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]