wicket-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabio Fioretti" <windom.macroso...@gmail.com>
Subject Re: Avoid page re-instantiation upon browser back button pushing.
Date Thu, 02 Aug 2007 16:32:44 GMT
On 8/1/07, Matej Knopp <matej.knopp@gmail.com> wrote:
> By default wicket doesn't send the no-store Cache header, so the page
> should be pulled from cache on back button. It's weird that the page
> is reloaded.

It really is, as it seems that every bookmarkable page isn't pulled
from cache over here...

> Anyway, new instance is created because there is a bookmarkable url.
> To creating new instances

I think you meant "to avoid the creation of new instances", didn't you?

> you'll have to either make the url
> non-bookmarkable (with the wicket:interface part), or you can mount
> the page using HybridUrlCodingStrategy (such as the ajax exampels
> are). To use this strategy you need the most recent wicket from trunk.

Ok, thanks a lot and thanks to all of you for your precious answers.


Kindest regards,

Fabio Fioretti - WindoM

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Mime
View raw message