You are right, I was not testing correctly. The pages were just cached and clicking on any non-bookmarkable link in them caused a page expired.
Thanks On Thu, Dec 10, 2009 at 6:11 PM, Matej Knopp <matej.kn...@gmail.com> wrote: > Are you sure you have been testing it correctly? The pagestore is > cyclic. That means once it reaches it's limit it's the oldest pages > get overwritten. > > -Matej > > On Thu, Dec 10, 2009 at 11:56 PM, Neil Curzon <neil.cur...@gmail.com> > wrote: > > Hi all, > > > > We're in the process of going live with our wicket app, so we're trying > to > > figure out certain details, currently PageStore size. > > > > I notice that by looking at the page store on disk, typically our pages > add > > 10-20kb each to the pagemap. The default 10mb limit would store a lot of > > pages, but we were thinking of using a smaller limit. I tried adjusting > the > > limit to 100kb, and as expected, the page store size capped out at about > > 100kb. > > > > I was expecting the consequence of this to be that the back button would > not > > work all the way to the beginning. Actually, what happens is that, after > my > > page map size hits the limit and stops growing, even if I continue to > click > > around the app for a while, I can still hit the back button all the way > back > > to the login, without hitting our "page expired" page. This surprised me. > Is > > this expected behavior? If the back button works with a 100kb page map > file, > > why use a 10mb one? > > > > Any help would be appreciated! > > > > Thanks, > > Neil > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
