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

From: Ryan Lubke <Ryan.Lubke_at_Sun.COM>
Date: Thu, 06 Sep 2007 14:43:31 -0700

Ryan Lubke wrote:
> Change bundle attached to the issue [1]
> The big question: Should serialization of server state be enabled by
> default or not?
My two cents:

 From a technical standpoint, having parity with client-side state
saving is a good thing.
We don't want two different behaviors depending on which type a client
application uses.

That said, this is the first report I've seen on this issue, but that
doesn't mean people haven't
hit it and worked around it. So, I'm fine with changing the default to
false and documenting
it's usage so if someone hits this in the future, then can flip this switch.

> [1]
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail: