>>>>> On Tue, 31 Jul 2012 09:04:48 +0100 (BST), Mark Struberg <struberg_at_yahoo.de> said:
MS> This basically comes back to the good ole browser back button handling.
MS> If you do _not_ serialize, then references stored in the state might
MS> all point to the same instance for different state versions. Thus
MS> you will accidentally (or rather 'blindly') change old view
MS> states. By serializing the state you can guarantee that this problem
MS> doesn't occur.
MS> Now you can argue that back button handling is most times broken
MS> anyway - but then you need to further ask why we store a state
MS> history at all?
MS>
MS> just my .02
MS>
MS>
MS> LieGrue,
MS> strub
MS> PS: for what it's worth. It seems that Wicket just recently went the
MS> other way and now forces serialisation. Of course that had a
MS> performance impact, but there might have been good reasons...
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/