News for hackers. Stuff that matters.
Re:Post-REST by naasking on Monday November 19, 2018 @06:16PM (#18490593)
> 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.

Re:Post-REST by marcosdumay on Monday November 19, 2018 @06:58PM (#18490801)
> 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.

Re:Post-REST by naasking on Monday November 19, 2018 @08:15PM (#18491146)
I meant server side state. Client provided data isn't state from the server's perspective.
Re:Post-REST by marcosdumay on Wednesday November 21, 2018 @04:03PM (#18506083)
We are talking about server transactions. It's server-side data sent by a client.