Re: [REVIEW/632] Server-side state saving sensitive to model changes

From: Ryan Lubke <Ryan.Lubke_at_Sun.COM>
Date: Tue, 11 Sep 2007 10:56:09 -0700

Ed Burns wrote:
>>>>>> On Fri, 07 Sep 2007 11:32:22 +0200, "Jesse Alexander (KSFH 323)" <> said:
> JA> +1 from me too on not making the serialization default. Serialization is
> JA> way too costly.
> I cast my lot with Herr Jesse and Mr. Winer. I too would like to see a
> quantitative rationale, other than parity with the client side model.
Performance issues aside (which we know there will be a decrease in
when this option is enabled), a JSF application should be have the same
when using
the default state manager no matter what option is selected.

For what it's worth, it seems MyFaces serializes server state by default
[1]. So a SEAM
application on MyFaces will behave the same no matter the state saving

I'm still torn on this issue. I think the correct course of action is
to enable the serialization by default,
but looking at the MyFaces benchmarks, performance is nearly halved in
this case and I really don't
know how often the case Mike is reporting will happen. Perhaps it will
become more common
as more folks move to SEAM?