Serializing server state final thoughts

From: Michael Youngstrom <>
Date: Wed, 12 Sep 2007 09:10:36 -0600

So, the the votes are in and it looks like the decision is to not
serialize the server state. However, does this snippet from the spec
make our vote irrelevant?

Section 7.6.3: when talking about server state management says:

"The default implementation Serializes the view in both the client and
server modes. In the
server mode, this serialized view is stored in the session and a
unique key to retrieve the
view is sent down to the client. By storing the serialized view in the
session, failover may happen using the usual mechanisms provided by
the container."

It seems pretty explicit here. This is probably why Myfaces
serializes the view by default in "SERVER" mode. Does this snippet
from the spec change our decision at all? If we decide to ignore this
snippet of the spec we should probably let MyFaces know so that they
don't have to serialize the view by default.