3 ms·
It bears noting that when people talk about REST(ful) APIs, they are not actually talking about strictly 100% pure REST. Some parts of the original REST spec ar
by argonaut 13y ago
It bears noting that when people talk about REST(ful) APIs, they are not actually talking about strictly 100% pure REST. Some parts of the original REST spec are impractical in practice (HATEOAS, anyone?) and are never used.
- dragonwriter 13y agoHATEOAS works pretty well for the web, so I don't know that I'd say its never used or impractical. Most people who talk about RESTful API's seem to use it as a term for RPC-over-HTTP without the overhead of SOAP, rather than to meaning anything with even a passing resemblance to what was described in Fielding's thesis.
- argonaut 13y agoIt's never used in RESTful APIs, which is what I mean.
- dragonwriter 13y agoAlmost none of REST is used in most "RESTful" APIs except incidentally, because "RESTful" APIs are usually simple RPC-over-HTTP, and have nothing to do with REST. OTOH, there are RESTful APIs that actually try to use REST, including HATEOAS, such as PayPal's [1]. [1] https://developer.paypal.com/docs/integration/direct/paypal-rest-payment-hateoas-links/ https://developer.paypal.com/docs/integration/direct/paypal-...
- aashishkoirala 13y agoThanks for the link to PayPal's API. I would be curious to know if doing pure HATEOAS like that has reaped any specific benefits for them.