4 ms·
"Basically misunderstood REST and added back the discoverability that was there to begin with" approach. You can see from his "proper" implementation of rest t
by LoSboccacc 8y ago
"Basically misunderstood REST and added back the discoverability that was there to begin with" approach.
You can see from his "proper" implementation of rest that his test understanding is partial at best, for example the user object doesn't return links to change his state (i.e. suspend, delete) not the users resource exposes an endpoint to add a user.
Then he added it in the "introspected" approach, but it's nothing novel.
- pojzon 8y agoI think that if discoverability would be there from the start, we wouldnt have things like Hateoas or GraphQL developed in the first place - why do that if its there ? First example shows how most APIs on Internet look like right now with all possible enhancments after that - presenting that they are far from ideal. After that is a section which shows how to limit human interaction with API because it should be "machine to machine" designed and how it can be accomplished using the new approach. Tho i understand its hard to get at first, some TLDR wouldnt hurt.
- icebraining 8y agoI think that if discoverability would be there from the start, we wouldnt have things like Hateoas HATEOAS is there from the start; in fact, it's an integral part of the concept of REST.
- naasking 8y ago> I think that if discoverability would be there from the start, we wouldnt have things like Hateoas HATEOAS is discoverable. That's the whole point of placing hypermedia as a central tenet of REST.
- LoSboccacc 8y ago> I think that if discoverability would be there from the start, we wouldnt have things like Hateoas Off you go into the heap of people that don't understand rest. Hateoas is in the original spec, if you haven't read it. > Tho i understand its hard to get at first, some TLDR wouldnt hurt. Maybe some reading of basic etiquette would help there too.