yeah because the default pagemap is never cleaned or removed..

But in the (what is now) default behaviour of 2.0 this doesn't matter because we only have 1 page in mem.
But There we don't need this window check at all for this particular case.
I know you subsessions but that is a different usecase and a different kind of thing in my eyes.
(subsession could container more then one window just fine)

johan


On 7/21/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> We do keep the problem Matej is describing.. If you are in the default
> pagemap when you hit for the first time
> And then you close the browser and come back. And the session is still there
> then the default pagemap will never be or
> used anymore because it will always redirect to another pagemap.

Yeah. It's not an urgent problem though. The only thing problem is
that it keeps the old pages around for the duration of the session.
That's acceptable imo for a case that won't happen often.

Eelco

-------------------------------------------------------------------------
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-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop

-------------------------------------------------------------------------
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-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to