On 2/15/10 4:24 PM, webtier_at_javadesktop.org wrote:
> Hrmm.. I might give that a shot tonight when I get a chance to work on the project again.
>
> What is the consequence of disabling partial state saving?
>
The runtime basically reverts to 1.2-style state saving (which could be
heavy on session
memory if using server side state saving. If using client side state
saving, then the page size increased
by quite a bit) :
- state will be saved and the tree 'serialized' when the view is saved
- when restoring, the 'serialized' tree is reconstructed without
consulting the template
and the state applied.
Partial state saving attempts to reduce the memory consumption or page
size by:
- mark the initial state of the view after the view has been
initialized by a GET.
- when saving the view, the tree structure isn't saved, but any state
changes
made to the component *after* the initial state has been marked
will be saved.
- when a view is restored due to a post-back, the view is
reconstructed by executing
the template (same as the GET case described above) and then the
delta state
is applied afterward.
> [Message sent by forum member 'mdergacz' (marc_at_skytix.com.au)]
>
> http://forums.java.net/jive/thread.jspa?messageID=386888
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webtier-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: webtier-help_at_glassfish.dev.java.net
>
>