| No, servers should hold _all the state_ and clients none. That's the opposite of the general consensus in the webdev-community. Client-state is not only vastly more efficient in many cases but it also usually leads to cleaner designs and easier scaling. Many of the modern desktop-like webapps would be outright infeasible without client-state. What's your response to that, should we just refrain from making such apps in the browser? If I add something to my shopping basket from my mobile phone, I want to be able to add more from my browser And at the same time you probably appreciate when on your slow mobile-link the "add-basket" operation happens asynchronously, yet doesn't get lost when you refresh the page at the wrong moment. I'm a bit confused here. You know better than most how critical latency is to the user-experience. Saving on server-roundtrips or hiding them is a big deal. Yet you promote this dogma without providing an alternative solution to this dilemma. |
That kind of cookie usage just makes it Somebody Else's Problem instead of your problem.