Currently - no. It holds the page *instances* from the last request. It may be one page or more, it depends on the logic in your code.
Most of the time this is enough. Pressing browser back button will go to second level cache, but any normal flow (clicking a link/button) will use the first level cache. On Fri, Jul 15, 2011 at 11:30 AM, Andrea Del Bene <[email protected]> wrote: > Thank you Martin, that's very useful! > I've got one question. Is there any way to set size of first level cache > (session scoped cache)? >> >> Hi, >> >> I just added a new wiki page labeled with "wicket15" about the >> implementation of IPageManager, IPageStore and IDataStore interfaces >> at https://cwiki.apache.org/confluence/display/WICKET/Page+Storage. >> >> Please review it and give feedback what is unclear/missing/wrong. >> >> The page describes how currently Wicket 1.5 stores the pages, what >> kind of caches are available and how to change some related settings. >> If you have idea how the whole thing can be further improved then >> don't hesitate to start a new thread to discuss the idea. >> > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
