On 7/17/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
wicket is a framework for dynamic webpages, so 99% of the time you don't
want to cache
and you want to make sure that the browser does query again for the page.
Also the none bookmarkable pages are like wicket:interface=xxxx and that xxx
can be anything
and 2 the same values could point to completely different things over
multiply runs of the browser.
if you want caching you have to do it your self in Page.configureResponse()
or in your Resources.configeResponse()
In both default imp we do already some stuff for example Page is configured
to not cache
and a resource if it is cacheable will send 2 headers. Also we have special
support for the head request: 'If-Modified-Since'
I agree with Johan, though giving it a serious look sometime wouldn't
hurt I guess. I think it wouldn't be very complex to look at. Bruno,
how about you write a little proof-of-concept?
Eelco
