Archive of UserLand's first discussion group, started October 5, 1998.
Review of updated SOAP spec
Author: André Radke Posted: 12/3/1999; 9:57:32 AM Topic: Review of updated SOAP spec Msg #: 13412 Prev/Next: 13411 / 13413
The SpecsPrevious version: http://www.ietf.org/internet-drafts/draft-box-http-soap-00.txt
New version: http://www.ietf.org/internet-drafts/draft-box-http-soap-01.txt
Namespaces
The new version places a stronger emphasis on using XML namespaces. All protocol tags should be scoped to the SOAP namespace. See Section 5 for the explanation and section 3.3 for examples.
POST vs. M-POST
The previous version mandated the prefered use of the M-POST HTTP verb over the regular POST verb. The new version does not mandate this preference. Actually, all requests should now first be made using the POST verb, and if they fail the M-POST verb should be tried. See section 6.2 for details.
HTTP Request and Response Headers
The previous version used "text/xml-SOAP" for the HTTP Content-Type header. The new version uses just "text/xml". See section 6.2 for details.
The previous version used "MethodName" and "InterfaceName" HTTP headers. The new version uses just "SOAPMethodName". See section 6.3 for details.
Structure of Request and Response Bodies
The structure of message bodies has been changed slightly by introducing an additional SOAP:Body tag.
The root element has been renamed from SerializedStream to SOAP:Envelope.
The headers element has been renamed from SOAP:headers to SOAP:Header.
The fault element has been renamed from __fault to SOAP:fault.
Parameter encoding
A new simple data type has been introduced: enum. See section 8.2.2 for details
Summary
The actual encoding of parameters has not changed except for the new data type. Most changes relate to the structure of the whole request and to how it's transmitted. It looks like most of the changes were aimed at making the spec more consistent.
This page was archived on 6/13/2001; 4:53:39 PM.
© Copyright 1998-2001 UserLand Software, Inc.