Re: the meaning of stateless
Mike Schinkel <[email protected]>
| Newsgroups | gmane.comp.web.services.rest |
|---|---|
| Message-ID | <[email protected]> |
On Apr 22, 2013, at 6:21 PM, Will Hartung <[email protected]> wrote: > All mentions of state within the context of REST is TRANSACTION state. A TRANSACTION is a process that CHANGES (Creates, changes, or deletes) a RESOURCE. > > The value of a resource is NOT "STATE". The back end application as represented by resources and resources have values, and REST systems then offer up REPRESENTATIONS of those values. Okay, I think I'm narrowing in on understanding, but still need a bit more help. > If you want to consider the combination of Resource values managed by the Application as "The State of the Application", then that's fine. But that "State" is not the same "state" that we talk about when discussing the "stateless" nature of REST architectures. I think I'm getting why these are not considered stateful, because you are differentiating between application state and some other kind of "bad" state, right? So if "application" state differs, what adjective do we apply to the "bad" kind of state? Also, can you give examples of bad state and explain why it's specifically bad in contrast to application state being okay? Many thanks in advance. This is really helping, at least it's helping me. -Mike