- From: Henrik Frystyk Nielsen <frystyk@microsoft.com>
- Date: Mon, 18 Dec 2000 13:56:53 -0800
- To: "Kevin Koch" <Kevin.Koch@realLegal.com>, <xml-dist-app@w3.org>
Hi Kevin, Before starting another major thread on this subject, you might want to have a look at [1]. Believe me, this has been discussed a lot but the major reason for doing it the way SOAP specifies is to not break HTTP. Btw, some people on this list responded [2] to [1] - you might want to read this too. [1] http://www.normos.org/ietf/draft/draft-moore-using-http-01.txt [2] http://lists.w3.org/Archives/Public/xml-dist-app/2000Dec/0178.html Henrik > This doesn't seem right. It also causes problems for people > wishing to > write simple soap clients. Many HTTP APIs handle HTTP errors very > differently > than standard returns. Depending upon the API, it is not > always possible to > > read the body of an error response. Further, in my opinion, > HTTP errors > should be reserved for actual HTTP server errors, not SOAP > request errors. > This type of functional overloading, although well intentioned, is not > appropriate.
Received on Monday, 18 December 2000 16:57:35 UTC