Hi Igor, I now understand why it's behaving as it is, but what do you exactly mean by A'->A''? That you are using the same objects whichever tab you click?
And when I revert back to the current 1.3 built, will this cache be on be default, or do I need to do something extra? Thanks, Wouter On 5/14/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > it is the same trick. he said its only turned off when only when you use > second level cache - the reason being that second level cache keeps a > complete clone of the page instead of the usual page+undo history. > > lets say you open page A(0) in tab1, 0 being the version number. you click a > link, that results in A(1). then you click another link and tell it to open > in a new tab. this will result in A(2) in tab2. > > so now what you have is > > tab1->A(1), tab2->A(2) > > now lets say you click a link in tab1. what will happen is that wicket will > apply the undo history to get the page to A(1) state, then execute the link, > which will result in A(3). this means that tab2->A(2), but A(2) is gone > because the page has been reverted. so now when you click on anything in > tab2 you will get a page expired error because it cannot get page A back to > version 2. > > now with second level cache the same scenario looks like this > > tab1->A. click on tab1 leads to tab1->A'. click and open in new tab leads to > tab1->A', tab2->A'' > so you see, with second level cache the versions _are_ the complete state of > the page, you dont lose anything by reverting back to a version because > there is no "reverting". > > so now if you click on something in tab1 your state will be > > tab1->A''', tab2->A'' > > hope this explains it. > > -igor > > > -igor > > > On 5/14/07, Erik van Oosten <[EMAIL PROTECTED]> wrote: > > > > But isn't that the same trick as in 1.2? > > Johan writes it is turned off in 1.3. He suggests that it will still work > > correctly. Maybe I understood wrong. > > > > Erik. > > > > > > igor.vaynberg wrote: > > > > > > we use a javascript trick. when a page loads into the window for the > first > > > time it sets the window.name variable to something other then null. in > new > > > windows this var is always initialized to null, so if we do a request > and > > > see that it is null we know a new window/tab has been opened. > > > > > > -igor > > > > > > > > > -- > > Erik van Oosten > > http://2007.rubyenrails.nl/ > > http://day-to-day-stuff.blogspot.com/ > > -- > > View this message in context: > http://www.nabble.com/weird-url-behaviour-for-bookmarkable-pages-tf3752813.html#a10608280 > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > Wicket-user mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
