When user presses the back button, wicket need to reconstruct the previous page instance. And the previous page instance is stored in second level cache. Wichet is a statefull framework, it maintains page instances. Most of the time the url only contains page id and page version. This is used to pull the right instance from second level cache.
-Matej On Nov 16, 2007 11:40 PM, mfs <[EMAIL PROTECTED]> wrote: > > Guys, > > I am yet bringing the same question again, regarding the SLCSS and the need > to maintain it the older versions of the page on the disk or otherwise...and > would really appreciate if some of my questions could be addressed here.. > > Before i go into Second Level Cache..i would say that i still can comprehend > the reason to store the latest version of a page (or the last accessed > version) in the session, since a user can click the browser back button and > access it (though by default this wouldnt happen and we would need to set > the header to "no-store" so that a request is sent to the server instead of > loading the last page from browser-cache)..or if we have a back button > functionality explicitly implemented on our page...or yet otherwise if the > user clicks the refresh button we can still utilize the last page-version.. > > Coming to the Second Level Cache, i still find it hard to understand as to > why and when would one come to the need of accessing the old serialized page > versions (other than the latest) ? what would those use-cases be when would > be want to access the earlier versions of a page ? Can someone point me some > of those scenarios... > > Thanks in advance and Regards, > > Farhan. > > > > > > -- > View this message in context: > http://www.nabble.com/Second-Level-Cache-tf4824369.html#a13803095 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
