6 ms·
> The reason you can't POST a transaction [1] is primarily that due to ~25 years of Web inertia that has hardwired people's brains into thinking that the reques
by naasking 8y ago
> The reason you can't POST a transaction [1] is primarily that due to ~25 years of Web inertia that has hardwired people's brains into thinking that the request lifecycle is that a request comes in, you deal with it, you emit your response, and then you drop all state on the floor.
I think that's still true if we're talking ephemeral state, like session data. Caching such data is an optimization, but conceptually we should be able to toss it at any point.
If you need to keep state, then it needs to be durable with a well-defined lifetime, and so this state should itself be a resource.
- marcosdumay 8y ago> If you need to keep state, then it needs to be durable with a well-defined lifetime Why? Why can't you drop it at any time and have the client repeat the interaction on any kind of problem? I'm not saying that it shouldn't be a resource either. Those things do not exclude each other.
- naasking 8y agoI meant server side state. Client provided data isn't state from the server's perspective.
- marcosdumay 8y agoWe are talking about server transactions. It's server-side data sent by a client.