Client-State Saving - which technique is used?

[bambata]

Hello,

I am writing my master thesis about Jboss Seam/EJB3/JSF and I am looking for some information about how the client-state saving takes place. In the Seam reference documentation is written the state is saved within the client browser. But where is the information exactly, is it in the cache of the browser, in a cookie or perhaps embedded in the html code as encoded information? How is that place in the browser accessible?

thanks in advance

hans

[gavin.king]

It is stored in the JSF ViewRoot attributes.

[shohei]

I also just thought about it.

Where has the server been switched to the client?
(Where does isClientSideConversations=true become it?)

Thanks

Shohei

[bambata]

Well, the UIViewRoot is the container for all controls on the Page and its the root element of the component tree.
However I actually wanted to know where the data is physically stored. I looked into some JSF books and found that client-state-saving puts the state into the rendered markup that is sent to the client, usually by using a large hidden html-input-field.

So, Seam puts the state information into the JSF ViewRoot Container and then delegates the responsibility for state-saving to JSF, and JSF is from that point on fully responsible for state-saving, is that correct?

[gavin.king]

Correct.

[bambata]

thanks