- From: Mountain, Highland M <highland.m.mountain@intel.com>
- Date: Tue, 26 Mar 2002 12:23:22 -0800
- To: "'Mark Baker'" <distobj@acm.org>, xml-dist-app@w3.org
Mark Baker's 192 proposal [1] is tagged more clearly, below. Sorry for any confusion generated by my previous email..... ============================================================ This proposal to 192 (especially the first point) and the discussion surrounding it seem contrary to R600. True, we are using the word should here, but additional discussions regarding other transports are implying a MUST tone. <Mark Baker's proposal for 192 (to be discussed at the 3/27 telecon)> What I suggest we do is; 1) update the binding framework to state that each binding should declare that the authoritative determinant of whether a message is a fault or not should be the underlying protocol 2) update the default HTTP binding to state that a SOAP Fault MUST only be processed as a SOAP Fault if the response code is 4xx or 5xx. </Mark Baker's proposal for 192 (to be discussed at the 3/27 telecon)> <R600> The XMLP specification must not mandate any dependency on specific features or mechanisms provided by a particular transport protocol beyond the basic requirement that the transport protocol must have the ability to deliver the XMLP envelope as a whole unit. This requirement does not preclude a mapping or binding to a transport protocol taking advantages of such features. It is intended to ensure that the basic XMLP specification will be transport neutral </R600> IMO, deriving Transport Binding Framework fault handling directives from HTTP binding specific issues(12 & 192) goes against R600. [1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x192 -----Original Message----- From: Mark Baker [mailto:distobj@acm.org] Sent: Saturday, March 23, 2002 4:53 PM To: xml-dist-app@w3.org Subject: Issues 12 & 192 All, I've been thinking some more about issue 12 and its relationship to issue 192. Issue 12 says; "A 2xx status code indicates that the request, including the SOAP message component, was successfully received, understood, and accepted by the receiving SOAP processor." This seems to me to exclude the possibility that faults (that are supposed to be processed as faults) should be returned over 2xx responses. IMO, issue 192 is simply asking that we explicitly state what issue 12 already implicitly suggests. Thanks. MB -- Mark Baker, Chief Science Officer, Planetfred, Inc. Ottawa, Ontario, CANADA. mbaker@planetfred.com http://www.markbaker.ca http://www.planetfred.com
Received on Tuesday, 26 March 2002 15:23:32 UTC