(AbstractLifeCycle.java:40)
at runjettyrun.Bootstrap.main(Bootstrap.java:121)
CC: users@tapestry.apache.org
From: lpri...@hope.nyc.ny.us
Subject: Re: Strategy for dealing with stale sessions?
Date: Mon, 13 May 2013 11:44:45 -0400
To: users@tapestry.apache.org
FlowLogix library handles
: Re: Strategy for dealing with stale sessions?
Date: Mon, 13 May 2013 11:44:45 -0400
To: users@tapestry.apache.org
FlowLogix library handles this generically by reloading the page if session
expired.
Take a look specifically at @AJAX annotation.
http://code.google.com/p/flowlogix/wiki
My application is heavily dependent on state using @Persist annotations. If a
user gets the application into a certain state, then their session becomes
stale (i.e. they leave their computer for half an hour), what is the preferred
approach for graceful recovery of the application now that the
I think this is an application-specific question. When the application
server's underlying session expires, all your @Persisted fields become
null, as you say. If the user continues, it's just as if a random, unknown
user arrived and attempted to start interacting with your application
somewhere
FlowLogix library handles this generically by reloading the page if session
expired.
Take a look specifically at @AJAX annotation.
http://code.google.com/p/flowlogix/wiki/TapestryLibrary
http://code.google.com/p/flowlogix/wiki/TLAJAXAnnotation
On May 13, 2013, at 6:24 AM, Ben Titmarsh
...@hope.nyc.ny.us
Subject: Re: Strategy for dealing with stale sessions?
Date: Mon, 13 May 2013 11:44:45 -0400
To: users@tapestry.apache.org
FlowLogix library handles this generically by reloading the page if session
expired.
Take a look specifically at @AJAX annotation.
http://code.google.com/p
