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
maybe wicket 2.0 will come with a TardisPageStore :)
-igor
On Fri, Dec 11, 2009 at 8:56 AM, Neil Curzon neil.cur...@gmail.com wrote:
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
did wicket 2.0 had a tardis??
i am checking svn right now for those lost diamonds!
On 11/12/2009, Igor Vaynberg igor.vaynb...@gmail.com wrote:
maybe wicket 2.0 will come with a TardisPageStore :)
-igor
On Fri, Dec 11, 2009 at 8:56 AM, Neil Curzon neil.cur...@gmail.com wrote:
You are right,
It's in the 2.0 in alternate future. Time travel is a tricky thing.
-Matej
On Fri, Dec 11, 2009 at 9:37 PM, Johan Compagner jcompag...@gmail.com wrote:
did wicket 2.0 had a tardis??
i am checking svn right now for those lost diamonds!
On 11/12/2009, Igor Vaynberg igor.vaynb...@gmail.com
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
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
