Unfortunately client side state is the only way to get multiple component trees to not conflict (IFRAME, popup windows, user has multiple windows open, etc). I am using server state and as a result, I cannot use some of these techniques (like the jenia4faces dialog).
If that was fixed (apparently it works in the JSF RI), I wouldn't see a very good use for the client side state. -Andrew On 5/22/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
Hi! >> Well, we use JSP to describe the JSF view too - we slowly convert our >> application from JSP to JSF (so we have both JSP embedded in JSF and >> pure JSF), and I cant say that the performance it that worse. >> > It can be that worse, actually, client side state saving is a huge > burden, but it does not have to be, the correct state saving strategy > (server side) can give a huge push. > Oh, well, for sure, and I dont know why one would like to use client side state saving in real live. Ciao, Mario
