just checked in a lot of changes regarding page maps and storage of page state into HEAD. because of the amount of change that happened, it's likely that HEAD is a bit unstable right now. i ran the unit tests and tested a bit on my pet application to make sure the basics work, but there
could be some problems.  any problems should be easy to fix though.

the major change is that PageMap now uses session attributes directly. this should save some memory and will make clustering replication more straightforward. the old MostRecentlyUsedMap class is no longer being used. instead, there is a resolution to bug 1238845 (Introduce a factory for MRUMap) since the new code allows you to install
any kind of eviction strategy you want for your page map.

there are some other changes, but i can't recall all of them at this time. please let me know how
it goes.

best,

        jon



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to