ZK - Open Source Ajax Java Framework

In my eyes i gave those peoples right. But it's use case dependent. For me the priority is more interesting that an application can high scaling and not the session failover. If the case occur that one server is failing than the user must do a new login. That's all. For uncomitted data the database must regulate this (Rollback).

best
Stephan

Thanks for your opinion. So you would follow "Lift people" on this subject on a general use case except when you're more intererested into scaling.

Here would be an approcah of David Pollak (creator of Lift) : "Here is On pages where the data really matters, you have to do a little extra work to capture things as the user is typing, putting this state information in a
more reliable store and if you have a node crash, you can still recover the user activity. I've been noodling with some wrappers (kinda like callOnce) that would insert the correct JavaScript into all the form elements and
capture stuff on the back end. This would be a higher bandwidth kinda thing and shouldn't be done for all forms, but could deal with the important forms/user interactions for stuff that's in a regulated environment. "

Regarding scaling, session affinity in pair with the load balancer is their position, mentionning that nothing avoid to have whatever we want behind the web framework, including a compute grid for example. They also claim session affinity having tremendous advantage to be very fast and with extended sessions enabled, the user does not have to login again (in cas of crash of the node he first logged in)