2 ms·
No, it isn't, and the fact that you found it to be useless in a JSON API is evidence for my claim. The problem here isn't the API you designed per se: sure you
by recursivedoubts 5y ago
No, it isn't, and the fact that you found it to be useless in a JSON API is evidence for my claim.
The problem here isn't the API you designed per se: sure you can encode a hypermedia on top of anything, even JSON. The problem is the clients aren't hypermedia clients and don't want to interact with the API in that manner. They aren't using hypermedia as the application of engine state, they aren't taking advantage of the uniform interface and all the rest of it. If you read "HATOEAS is for Humans" I try to explain why that is.
All the problems you are pointing out are due to the fact that your hypermedia-on-top-of-JSON API is being consumed by non-hypermedia clients who, at the end of the day, just want a powerful RPC/Query mechanism. Which is fine, I'm glad you came to your senses and gave that to them.
But, to return to the original point, if you are just trying to get forms into databases, hypermedia is much simpler.
- halostatue 5y agoI read your articles. I disagree with your foundational premise. HTML is a presentation / structure mechanism. HATEOAS isn’t _only_ for humans, but HTML is. The APIs that I built _were_ hypermedia. The only way to properly use them was to follow the links in the data. The problem wasn’t the APIs or even the software clients. It was the developers who didn’t see the point of it and ended up developing versions that broke the pattern. If all you have to worry about is a web browser, then you can start from your foundational premise. Most of us have to deal with all sorts of clients.
- recursivedoubts 5y ago> It was the developers who didn’t see the point of it and ended up developing versions that broke the pattern. lol, cool man, take a week or two to think about that and then maybe reread my article :beers: