So i guess one of the things i misunderstood earlier was that i assumed that the pageMap maintains the latest page-instance/version (in the active session) of all the different page-components, but as it turns out its just the latest accessed page's instance which is kept in the session, and hence just one active-page in session at one time, all other instances of different page-components are serialized to the disk.
I understand that the browser back button doesnt really come in the above context, but you agree to the fact that one has to do a no-store to actually LET wicket load the page from the SLC otherwise this back button support by wicket (which is considered to be one of the main features of it) wouldn't really come into play? Thanks again man..you guys are doing a great job..! Farhan. Johan Compagner wrote: > > No it is a bit different > the SLC is for back button support. > The reason that we have the latest page in the session is because thats > the > live > page where all the action is on. So that page is NOT used when the users > hits the backbutton > that page is only used when the users clicks a link or submits a button or > triggers an ajax event. > When the users hits the backbutton then the SLC comes into play and will > reload that > previous page from disk. If you do no-store that doesnt matter in that > area (that only annoys users) > because the page is read earlier from disk then when you don't have > no-store > (with no-store > immediantly when the users hits the back, else only when a users does > something on that page) > > johan > > > > 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<http://nabble.com/> >> . >> >> >> --------------------------------------------------------------------- >> 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#a13815164 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
