Speaking of this, I had the same issue recently.
I wished for stateless pages but as I didn't know, I opted for
"keep-alive" ajax requests.
Is there some article, blog, tutorial or whatever on how to keep pages
stateless?
I know that "if a page is bookmarkable and doesn't contain any
non-stateless components/behaviors then the page is automatically
stateless and not stored in the session",
but that mostly excludes ajax.
There's no "keep just one page state and always use it" trick? Would it
work if some PageStore impl behave like that?
Ondra
On 01/21/2013 10:35 PM, Martin Grigorov wrote:
Well, I'll need some more technical details about Tapestry internals to
understand what they do.
You can check https://github.com/jolira/wicket-stateless - it provides few
Ajax behaviors and components which are stateless, i.e. they re-create the
whole page for each request.
I think this is what you are looking for - stateless pages.
On Mon, Jan 21, 2013 at 11:18 PM, sthomps <stho...@gmail.com> wrote:
You can read the Tapestry response a
href="
http://tapestry.1045711.n5.nabble.com/Session-Expiration-Ajax-td5719213.html
">here.
Essentially there are no PageMaps/versions per users session.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-Session-Expiration-Ajax-interactions-tp4655591p4655604.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
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
