Other interpretations of this have lead to what is effectively the opposite of "stateless" design. Lift and a few other frameworks work by modeling the page session on the server and letting the browser just be a render target -- to the point where you could have click events handled server side. Yes, the latency stinks in many cases so it didn't work out quite as well and more logic started moving onto the client.. but that was X over WAN's failing as well, so we collectively re-learned that lesson.