3 ms·
> But state is integral to the experience of a web application HTTP is a stateless protocol and the desire to maintain a state-full session on the server is wh
by 0x445442 7y ago
> But state is integral to the experience of a web application
HTTP is a stateless protocol and the desire to maintain a state-full session on the server is why web applications are fundamentally broken, at least within the context of HTTP.
- colanderman 7y agoRight, which is why session state should be kept on the client, and why the client should manipulate application state (i.e., everything that lives in a database) using a well-defined RESTful interface. The approach in the OP seems to conflate these two types of state. The end result is application state without a well-defined client interface, and session state which is passed backed and forth to the server.
- deleted 7y ago[deleted]
- amelius 7y ago> The approach in the OP seems to conflate these two types of state. Nope, I'm just saying that continuations and REST are orthogonal.