FW: XMLP WG Issue 342 Resolution
"Champion, Mike" <[email protected]>
| Newsgroups | gmane.comp.web.services.ws-arch |
|---|---|
| Message-ID | <[email protected]> |
Another response from XMLP ... -----Original Message----- From: Asir S Vedamuthu [mailto:[email protected]] Sent: Thursday, August 01, 2002 4:25 PM To: [email protected] Cc: [email protected] Subject: XMLP WG Issue 342 Resolution Mike, The XML Protocol (XMLP) WG has decided to close issue 342 [1], which you originated, with the following resolution. Issue 342 is a DUPLICATE of issue 224 [2]. WG resolved issue 224 by adding the following paragraph to section 7.5.1.2 "Requesting" near Table 17, "Table 17 details the transitions that take place when a requesting SOAP node receives an HTTP status line and response headers. Table 17 refers to some but not all of the existing HTTP/1.1 [RFC 2616] status codes. In addition to these status codes, HTTP provides an open-ended mechanism for supporting status codes defined by HTTP extensions (see [RFC 2817] for a registration mechanism for new status codes). HTTP status codes are divided into status code classes as described in [RFC 2616], section 6.1.1. The SOAP HTTP binding follows the rules of any HTTP application which means that an implementation of the SOAP HTTP binding must understand the class of any status code, as indicated by the first digit, and treat any unrecognized response as being equivalent to the x00 status code of that class, with the exception that an unrecognized response must not be cached" We trust that this resolution satisfies your concern. If not, please contact the WG asap. [1] http://www.w3.org/2000/xp/Group/xmlp-lc-issues.html#x342 [2] http://www.w3.org/2000/xp/Group/xmlp-lc-issues.html#x224 Regards, Asir S Vedamuthu (for XML Protocol WG) webMethods, Inc. 703-460-2513 or [email protected] http://www.webmethods.com/