From WS-HTTP talking about SOAP vs. REST style interfaces:

  • WSDL can describe bindings of operations to many different protocols, but most bindings are to SOAP.
  • SOAP can be transported across many different protocols, but most SOAP messages are transported over HTTP.
  • Individual SOAP messages may have many different headers, but most don't have any.

    • Each of the above statements is arguable, but one thing that is undeniable is that a large number of people have found "simple XML over HTTP" to be a sweet spot.

Later on in the comments Ole Eichhorn has a good quote:

This makes too much sense, it could never happen. Adapt a standard to real world examples? Learn from actual usage patterns to determine what the standard should contain? C'mon Sam, this is too reasonable!

Trackbacks

Comments