Re:REST in peace, SOAP
by mkramlich on Friday October 15, 2010 @04:20PM
(#1796102)
How about we call something a HTTP-based API, when we want to distinguish it from full REST, or SOAP, etc? Or say JSON/HTTP or XML/HTTP.
[ Parent
| on HN ]
And how do you define whether something is "HTTP-based" or not? Because using HTTP is not quite a good enough condition: SOAP can use HTTP as a transport, and XML-RPC has always done that (I'm not sure it allows any other transport).