7 ms·
No HATEOAS? https://en.wikipedia.org/wiki/HATEOAS https://en.wikipedia.org/wiki/HATEOAS I don't think full-on HATEOAS is practical, and blog (https://jeffknup
by nwatson 7y ago
No HATEOAS? https://en.wikipedia.org/wiki/HATEOAS https://en.wikipedia.org/wiki/HATEOAS
I don't think full-on HATEOAS is practical, and blog (https://jeffknupp.com/blog/2014/06/03/why-i-hate-hateoas/ https://jeffknupp.com/blog/2014/06/03/why-i-hate-hateoas/) says it well: "When designing a hypermedia API [per HATEOAS standards], you're really designing for a client that does not, and will never, exist." There are some good ideas there though.
- jmull 7y agoI'm not sure the criticism in that blog has much to with anything. HATEOAS is about an approach to managing application state, not self-documenting APIs. I suppose it still gets at the big problem with a restful approach: nobody really gets it. (Personally, I think there are some great ideas in that dissertation, but HATEOAS isn't one of them. At least as far as I can tell.)
- naasking 7y agoHATEOAS is a good idea as well. It formalizes an idiom for schema upgrade and discovery.
- geezerjay 7y ago> No HATEOAS? https://en.wikipedia.org/wiki/HATEOAS https://en.wikipedia.org/wiki/HATEOAS HATEOAS is not a standard nora specification. It's a basic part of the REST architecture style. > "When designing a hypermedia API [per HATEOAS standards], you're really designing for a client that does not, and will never, exist." I don't believe this is factual or even conceivable. Arguably, OData speficies a standard that designs clients and servers that are full-on REST (per HATEOAS standards) and it does exist and is used in the wild for some years now. Additionally, there are other standards and specs that do help to implement full-on REST, such as HAL or JSON-LD.
- treve 7y agoA client: https://github.com/evert/ketting https://github.com/evert/ketting