On 5/22/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
>> 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.
I only use client-side state saving in my applications. client-side state saving eliminates the back button problem, and it can survive the death of the application server transparently. There's also no issues with session timeouts. Functionality trumps performance in my applications. At some point in the future, new hardware will eliminate the performance issues, but buying new hardware will never make my applications more functional.
