We have a problem here when working with popups and expiry of pages.
If we let, a page (say page 0 in the session) open a popup (will thus be page 1 in the session), and we leave this popup open and continue working on page 0, the popup page will be marked expired (HttpRequestCycle):
// Set the page for the component as the response page and expire any
// pages in the session cache that are newer than the
// given page since they will no longer be accessible.
setPage(page);
session.expireNewerThan(page);
This is wrong when working with pop-ups. Also, though I understand that for memory consumption it is nice to get rid of the pages as quickly as possible, without marking this newer page as expired the page will be removed automatically when the the page list in the session is exceeded, right?
I'd like to propose to remove the expire trick (thus delete session.expireNewerThan(page);).
Eelco
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
