btw, gere is an interesting point, where IE and Firefox differ from each
other. If you click the back-button of Firefox the page does not reload but
is loaded from cache.
http://blog.httpwatch.com/2008/10/15/two-important-differences-between-firefox-and-ie-caching/
maybe cache-control should be
This has been discussed before (of course) and this is on purpose. If
you reload old pages your users will probably wonder what's going on
(they are not used to this behavior), and secondly there is a
performance hit with no business benefit.
However, you should feel free to change these
I am reading the book Wicket in Action. Page 88 about serializing models says:
At the end of the request, after the markup has been sent to the browser,
Wicket stores the page, component hierarchy, and associated models (the state)
in the page store.
Does Wicket stores the page means Wicket
the serialized form of the page hierarchy is stored., you mean the
first two things?
Regards,
David
--- On Sun, 2/21/10, Erik van Oosten e.vanoos...@grons.nl wrote:
From: Erik van Oosten e.vanoos...@grons.nl
Subject: Re: Questions about how wicket serialization works
To: users@wicket.apache.org
Date
Wicket stores
1. the page,
2. component hierarchy,
3. and associated models (the state) in the page store.
By only the serialized form of the page hierarchy is stored., you mean the
first two things?
The page == component hierarchy and associated models are part of it
because they are
Answers below...
David Chang wrote:
I am reading the book Wicket in Action. Page 88 about serializing models says:
At the end of the request, after the markup has been sent to the browser, Wicket
stores the page, component hierarchy, and associated models (the state) in the page
store.
