>From: Michael Jouravlev <[EMAIL PROTECTED]> > > Can JSF store component state completely on client, that is, using > Javascript objects? I could not find anything besides _viewstate-like > juggling between client and server. >
JSF has an option to store the state of the page as a hidden field in the client. It's serialized objects that represent the component tree. Client state is more for handling the browser back/ dirty page more than making state available for javascript. > I think it would be nice if an application could try to save viewstate > on client, and if Javascript were turned off, the viewstate would be > submitted to server and stored there in the session. > It's a global on or off switch now. It would be nice if the client state was something usable by javascript. Shale is working on an idea of decorating renders so that you can modify the default content without having to know allot about the component. For example, you could intercept the generated html and write javascript to write dhtml. Or, add some ajax features to a component. I was talking with David Geary and he would like to see tiles hook into AJAX so that you could control the content of a DIV tag like you might a iframe. I guess this would be like creating a view root as a leaf node in the component tree representing the page. This is still kind of blue-sky stuff. Craig responded with a few comments from planet reality that I'm still trying to get a handle on :-). > Michael. > Gary > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
