On 1/23/06, Gary VanMatre <[EMAIL PROTECTED]> wrote: > >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.
This is what I call _viewstate juggling, hate it. Is it different from similar thing in ASP.NET? On 1/23/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > Yes, that's correct... with every document loaded into the > browser, anything that existed before is wiped out. I'm not aware of any > way around that (and it sure sounds like a security problem if there was). > A hidden frame is the typical solution in such cases... So, there are ways besides Ajax? This is good to hear. > Of course, now > you can do it with AJAX... you load one page in the beginning that > contains your AJAX code and a single <div>... every request you make to > the server goes through an XMLHttpRequest object, and the results are > stuck into that <div>... this can be a whole page, so in a sense your > creating a browser inside a browser :) Yeah, I know, I do that myself. I was curious about independent pages. This hidden frame thing... Can it work while actual page content is changed *and* page address is updated in the address line? Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
