Ashley Aitken wrote:
So the pages are only serialised when the session is serialised for replication. I am not sure how Wicket (or if it is even within Wicket's scope) handles replication/clustering, but if one were using sticking sessions (sessions mapped to the same server in the cluster) then I guess one wouldn't need to serialise the session or pages at all. Does that sound right?
Pages are also serialized when a new browser window is opened - the current page is cloned (via serialization) and placed in a new PageMap. This would occur, for example, if the user clicks on a link to your site in an email which usually opens the page in a new window. Also when a your page creates a pop-up window explicitly or the user opens a link in a new tab.
I don't fully understand why wicket needs to clone the page rather than just moving the page into the new page map?
John ------------------------------------------------------- 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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
