Eelco Hillenius wrote: > > Well, every user (session) will use memory, correct. But only to a > certain limit. Wicket 1.2 holds a couple of page/ versions in a > session, and Wicket 2.0 by default only holds the current one. So the > creation of a fresh instance (e.g. a bookmarkable page) will replace > another one. Hence, how much memory you'll need is a simple function > of the number of concurrent sessions times the size of your session > and page(s) in it. >
How can I instruct Wicket not to maintain the multiple versions of a given page within the session? I've tried the following but when I dump the session contents I still see multiple page versions: getSessionSettings().setMaxPageMaps(1); getPageSettings().setMaxPageVersions(1); Am I missing the boat on this entirely? -Jason -- View this message in context: http://www.nabble.com/Strategy-to-avoid-new-instances-of-pages-and-panels-tf2566413.html#a8553452 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user