Hi! > 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. Ok, I understand, in the past I also used client-side state saving, but things happening lately showed me that in the end I cant stick with it. Transparent persistence (hibernate) - "application transaction" - to tell only the headlines ;-) require to NOT serialize/deserialze your state (the upcoming conversationTag will help here), thus you can switch to server-side state saving as e.g you cant restore the state if it timed out so client-side ss wont help much.
But for sure, I am only one and using client-side state saving is more unproblematic. BTW: to workaround the session timeout problem we have a very small iframe on our page which will refresh itself every say 5 minutes. Thus the session wont die as long as the browser is open :-) Ciao, Mario
