On Tue, 08 Mar 2005 08:42:00 -0800, Jonathan Locke wrote:
>if xstream doesn't have downsides and is more efficient and we don't
>care about vm requirements, we could use xstream for undo cloning
>operations. then if we provided XStreamPageState, you wouldn't have to
>make anything serializable. (uh... i think). xml seems like a terribly
>verbose format though. i'm concerned about memory impact...
It goes hand-in-hand with Wicket's goals: ease of use and
development over performance (within reason). If you are concerned
about the memory impact you can:
a) Use the compact persistance plugin for XStream (it lets you
customize the XML format and compact is one of the preexisting plugins)
b) Compress it using zip before persisting
If I understand correctly: we only need to load/save at
startup/shutdown time which means that once loading is done you could
garbage collect that variable so no long-term memory impact there.
Gili
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
