Well i think it is required, at least as far as the browser back button is concerned (which is one of the features of wicket i.e. "back button support"), unless otherwise as you said where one explicitly wants to make a call to the old versions, but even with that i wonder how would one go about maintaining the references to these older page versions (so as to access it at later pages)? and lets just say even we do explicitly maintain them somewhere (e.g. in the session itself OR pass it from the previous pages), i think one wouldnt come to the need of referring the older versions of their components from within their application (except for the last couple of pages).
Farhan. Eelco Hillenius wrote: > > On Nov 17, 2007 4:58 PM, mfs <[EMAIL PROTECTED]> wrote: >> >> So basically i meant setting "no-store" in your response header so that >> the >> browser doesnt load the page from its local-cache, and instead sends the >> request to the server and let wicket load the last serialized page. > > I don't think it needs that, as it doesn't have to do the actual > reloading until you actually trigger a call back to that page (such as > a link or form submit). And those call backs will have the version > info in them. > > Eelco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Second-Level-Cache-tf4824369.html#a13815526 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
