W3C home > Mailing lists > Public > www-tag@w3.org > March 2002

RE: SOAP breaks HTTP?

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Mon, 25 Mar 2002 19:22:23 -0800
Message-ID: <79107D208BA38C45A4E45F62673A434D06DEE336@red-msg-07.redmond.corp.microsoft.com>
To: "Paul Prescod" <paul@prescod.net>, <www-tag@w3.org>

Might be worth pointing out that SOAP is a wire protocol, it is not an
application architecture. Indeed the RPC convention (which doesn't
define an architecture in any way) is separate from the HTTP binding and
by no means have to be used with SOAP over HTTP or in any other
combination. FWIW, I can write a tightly coupled application in HTML
form using HTTP POST if I wanted to - I can even write applications that
assign unintended side-effects to HTTP GET. 

What you are saying is really that RPC is bad and I am not the one to
disagree but your argument comes down to saying that HTTP POST is evil
which I think is stretching it a fair bit.

>Yes, but I would put it somewhat stronger: RPC over HTTP breaks
>architectural principles of the Web that were first described in 1996.
>http://www.w3.org/DesignIssues/Axioms.html#state

>6) SOAP adds features to HTTP but it is not clear how to use those
>features AND use HTTP methods with their appropriate semantics. For
>instance how can I use SOAP headers to do routing or signing in a
>GET/PUT/DELETE?

...and how do I use HTML form-based file upload [1] with HTTP DELETE
(not to mention, where does the notion of a file come from)?

Henrik

[1] http://www.normos.org/ietf/rfc/rfc1867.txt
Received on Monday, 25 March 2002 22:22:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:05 GMT