Yes that client-side-state setting does push only the JSF component tree
state into the page.
However the Tomahawk t:saveState tag pushes any arbitrary value into the
component tree, so t:saveState + client-side-state-saving combined can
probably do what you want.
Regards, Simon
Adam Winer wrote:
It only affects the UI tree state. The HttpSession stays
on the server.
BTW, just to make things *even more* complicated,
in Trinidad, setting "client" doesn't actually move all the
state to the client, it just sends a token down. That
can be overridden with a second config parameter that
forces all the state to be sent to the client, but again,
that's still just UI state.
-- Adam
On 5/11/07, lightbulb432 <[EMAIL PROTECTED]> wrote:
When you specify client-side state-saving, are you specifying that it be
serialized to the client only for the UI tree, or even for the
HttpSession
and other server-side session information?
I'd like to serialize such session state to the client, to make
clustering/load-balancing very easy, as there's no server-side session
state
stored - would this be possible?
--
View this message in context:
http://www.nabble.com/Client-side-state-saving-tf3727787.html#a10433169
Sent from the MyFaces - Users mailing list archive at Nabble.com.
