That's useful enough that someone should add a JIRA issue suggesting we supply that as a standard component.
On 3/22/07, Kristian Marinkovic <[EMAIL PROTECTED]> wrote:
i think a better strategy is to reduce the sesion-timeout in the web.xml to lets say 2mins and to implement a javascript function that issues periodic keep-alive requests every 1.5mins or so. thus preventing the session from expiring... and when someone closes his browser the session will not stay in memory for too long :) g, kris Tim Sawyer <[EMAIL PROTECTED]> 22.03.2007 11:10 Bitte antworten an "Tapestry users" <users@tapestry.apache.org> An users@tapestry.apache.org Kopie "James Sherwood" <[EMAIL PROTECTED]> Thema Re: Session I believe the timeout for this is configured through web.xml <session-config> <session-timeout>30</session-timeout> <!-- minutes --> </session-config Tim. On Tuesday 20 March 2007 17:16, James Sherwood wrote: > Hello, > > We have an admin side with a user login etc. > > The problem is, the session times out after soo many minutes(we run under > tomcat) of being idle and they user has to log back in. > > Is there any way to make this indefinate and if so, is there any impact on > resources etc? > > Thanks, > James > > > --------------------------------------------------------------------- > 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]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
