10871Re: REST: The short version
- Jun 1, 2008Hmmm I don't think we are that far off...
> I didn't get such a different reading from Mike's article, but Ithink I have
> a different view of the Hypermedia constraintÂ¹ than you doâ¦Agreed. That is what I meant when I said "and usually navigate to that
> The client doesn't only execute GETs to transition between states, POSTs
> transition between states just as well.
state in one step". When you are looking at things from a state
machine perspective, POST is often like a request that says "Please
add the state described in the body and transition me to that new
state". Though its not necessarily always like that I suppose. It
could perhaps be generalized to something like this: "Please change
the state machine as described in the body and transition me to the
state that represents my changes"?
> The client doesn't *change* the state machine, per se â¦ it merely
> between the states allowed by the server, as described by thehypermedia.
> Those transitions might end up mutating the state machine, butthat's not the
> same as the client mutating the state machine.So I agree that the server is changing the state machine in response
to the requests from the client. The client can't directly change the
state machine (i.e. the resources) -- it has to ask the server to do
it on its behalf. The requests made by the clients effect the changes
to the resources/state machine performed by the server (though of
course resources could change for other reasons -- e.g. a resource
that represents the weather in New York).
Was I missing something other than the server being involved though?
>Ya, HATEOAS is a mouth-full... but I think the "engine" and
> Â¹: I think "HATEOAS" is a bad name. "Hypermedia constraint" is more
> descriptive, and less "HATE"-filled. :)
"application state" parts are important as well. I think they
represent specific areas where attempts at REST tend to fall short.
- << Previous post in topic Next post in topic >>