On Apr 29, 2006, at 12:01 PM, Eelco Hillenius wrote:
We need to know when we can ditch the pages too. In the strategy you propose, we would ditch the second page in history - we always need to keep one to have a path for callbacks (links and forms). This would work exactly the same as doing getPageSettings().setMaxPageVersions(2) in your application's init() function. But... the problem would stay exactly the same as the the page you would need to the first tab/ window gets removed whenever you interact with the second tab/ window. The problem is that without those page maps, Wicket doesn't see the difference between requests comming from different windows. For example: if you have tab A and tab B, and both have the same pagemap, clicking a link on tab B, and then one on tab A is effectively the same as clicking a link on tab A, pushing the back button and clicking a link on tab A again. The only way to have this work is to increase your maxPageVersions size (but that will also increase the size of server memory you need for each session) or using different pagemaps. Pagemaps were always meant for this, but what we recently did was to build in automatic detection.
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.
I'm not convinced this is a good solution, but I'm concerned that most people are ignoring this problem. I love everything about wicket, except this. In this regard, wicket is a giant step backwards from other frameworks like webwork, struts, etc.
Michael Day ------------------------------------------------------- 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&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
