Re: IDEA: client-side state manager that restores majority of saved state from initial tree state

2007-01-07 Thread Martin Marinschek
I wonder how we can handle the case of adding components programmatically with this approach. @Jacob: Have you thought up a solution for this? regards, Martin On 12/22/06, Mike Kienenberger [EMAIL PROTECTED] wrote: Yes, my idea was probably partially inspired by things I read over the last

Re: IDEA: client-side state manager that restores majority of saved state from initial tree state

2007-01-07 Thread Jacob Hookom
It would be fine, just not included in the eden state-- Facelets would provide the eden state, then at the time of savestate, it would be compared to the passed component tree, only saving deltas. Until we get out of hierarchical state saving logic, we're going to be stuck with too much state

Re: IDEA: client-side state manager that restores majority of saved state from initial tree state

2007-01-07 Thread Jacob Hookom
Either that, or the eden state is assigned at first call to savestate-- so the initial accessor of the view would basically have an empty view state, since their would be treated as the benchmark for all others. This would allow incorporation of programmatically added components (as long as

Re: IDEA: client-side state manager that restores majority of saved state from initial tree state

2006-12-22 Thread Igor Shabalov
Seems like the subject nether become obsolete nor irrelevant from the beginning of 2006. I mean it is still important for may (including myself) and not yet resolved. IMHO the statefull nature of JSF is most obvious problem of this technology. I wonder if we can come up with some solution

Re: IDEA: client-side state manager that restores majority of saved state from initial tree state

2006-12-22 Thread Mike Kienenberger
Yes, my idea was probably partially inspired by things I read over the last year so it's probably not all that original. Glad to see I'm on the right track. It does sound like creating an alternate StateManager (which is within the JSF Spec) can accomplish this when using Facelets. I might

IDEA: client-side state manager that restores majority of saved state from initial tree state

2006-12-20 Thread Mike Kienenberger
I'm a fan of client-side state saving. It solves a lot of issues for me. However, there's no doubt that it requires more bandwidth due to saving the entire component tree state in a hidden input field. I wonder how much of this is really necessary. I'm guessing 90% of the state saved is

Re: IDEA: client-side state manager that restores majority of saved state from initial tree state

2006-12-20 Thread Thomas Spiegl
Maybe you can take a look at the Trinidad approach. I think Trinidad solves state-saving more effective than tomahawk or myfaces does. On 12/20/06, Mike Kienenberger [EMAIL PROTECTED] wrote: I'm a fan of client-side state saving. It solves a lot of issues for me. However, there's no doubt

Re: IDEA: client-side state manager that restores majority of saved state from initial tree state

2006-12-20 Thread Jacob Hookom
Adam Winer (Oracle ADF), Ed Burns (JSF Co-Spec Lead), and myself talked about this in combination with Facelets at JavaOne last year, we actually have some numbers generated: http://weblogs.java.net/blog/edburns/archive/2006/05/javaone_video_a_1.html (video, excuse my Minnesota slang)