3 ms·
You are technically correct, best kind of correct! I'd love to see a relatively non-obscure example of REST run over to a non-HTTP protocol. REST feels sort of
by nine_k 11y ago
You are technically correct, best kind of correct!
I'd love to see a relatively non-obscure example of REST run over to a non-HTTP protocol. REST feels sort of natural over HTTP, with all these URIs and HTTP method verbs.
XMLRPC has all the disadvantages of REST listed in the original article, but seemingly none of the advantages (like a logical, discoverable structure). Correct me if I'm wrong.
SOAP indeed has advantages — it has WSDL! When done correctly, it's delightful to work with. It's complicated and enormously more bloated, though. When run over HTTP (that is, most of the time), SOAP suffers from the same transport- and connection-related disadvantages as REST over HTTP does.
- dragonwriter 11y ago> I'd love to see a relatively non-obscure example of REST run over to a non-HTTP protocol. HTTP itself is the prototypical example; it is REST over an unspecified lower-level transport protocol (usually, in practice, TCP/IP, but that's explicitly not required in the spec) in the same sense that REST APIs that we usually talk about are typically REST over HTTP.