3 ms·
REST isn't appropriate as a description of JSON-based apis because JSON isn't a natural hypertext and thus makes HATEOAS difficult to implement. Most JSON APIs
by quantumofmalice 9y ago
REST isn't appropriate as a description of JSON-based apis because JSON isn't a natural hypertext and thus makes HATEOAS difficult to implement. Most JSON APIs described as REST are really RPC APIs with a bit of URL layout taken from the REST world.
Unfortunately XML-RPC was such a nightmare that calling something JSON-RPC was out of the question. Shame.
There are a few blog posts up on the intercooler website that discuss this that I found enlightening:
http://intercoolerjs.org/2016/01/18/rescuing-rest.html http://intercoolerjs.org/2016/01/18/rescuing-rest.html
http://intercoolerjs.org/2016/05/08/hatoeas-is-for-humans.html http://intercoolerjs.org/2016/05/08/hatoeas-is-for-humans.ht...
- thehardsphere 9y agoThere is a thing called JSON-RPC: http://www.jsonrpc.org/specification http://www.jsonrpc.org/specification The author explicitly mentions it as something he prefers over REST (though he spends more time on XML-RPC)