Currently we are removing pages from the PageMap in 2 places
First on new page (put) throw the eviction strategy.

and Two on access:

For example if the stack is Page1, Page2 and Page3
Then if you touch/render page1, page2 and Page3 are removed. Because we thread it as a browser stack
But this is ofcourse 2 windows or tabs or a popup on the same pagemap we have a big problem
because we get a page expired page. So i think this is bad default behaviour.

My vote would be to remove the on access and make the pagemap not a Browser stack but a last used queue
And use only the eviction strategy (on new page put) to remove pages.

The drawback is then that we don't remove pages as much as before. But with the multiply tabs and windows we really
can't guarantee anything so we just can't have a browser stack..

Anybody has a better idea to refactor it?

johan


On 3/20/06, SourceForge.net <[EMAIL PROTECTED] > wrote:
Bugs item #1454904, was opened at 2006-03-20 22:15
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1454904&group_id=119783

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Matej Knopp (knopp)
Assigned to: Nobody/Anonymous (nobody)
Summary: Make PageStack behave more like PageMap

Initial Comment:
Starting with version 1.2 the original behaviour of
PageMap was changed so it acts more like stack. E.g.
all pages newer that current rendered page are
automatically removed from pagemap.

While this saves some memory, it causes a big problem
when user wants to use the application in two tabs /
windows.

The solution would be to at least make configurable,
whether newer page than current should be automatically
evicted from pagemap.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1454904&group_id=119783


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to