So the question is how can we keep multiple instances of the same page in session, correct? What about keeping all pages (up to the configured max) in the session until the session expires? Once the number hits the max, remove the oldest (by time, not by "path"). So if a user has two tabs open, both would work for a long period... If he leaves one tab for an extended period, it would expire.
The good news is that you can implement any strategy for page history you like by providing your own implementation of IPageMapEvictionStrategy (getSessionSettings().setPageMapEvictionStrategy). If you find a strategy that works better - or which would be at least an alternative that might be attractive for certain situations - we'd be interested to know. If we agree to it's usefulness we could ship it with the Wicket distro. Eelco ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
