Comments on SOAP Version 1.2 Part 2: Adjuncts

As per my action item, I am continuing to read SOAP version 1.2 Last Call
Working Drafts.

Here are some architectural comments about SOAP Version 1.2 Part 2:
Adjuncts[1].

Part 1 and part 2 are the main parts of the specification. I am not
sure that I will have the time review part 0 and the test suite, but I
believe that part 1 and 2 are the important pieces for us. Maybe Anne
and Yin-Leng will get to them.

1) Architectural note: Web Method Feature (for the HTF)

SOAP defines a Web method feature which expresses the Web method (GET,
POST, DELETE, ...) to be used by the undelying protocol while
tranfering a SOAP message.

There is an explanation about how that relates to RPC usage in section
4.1.2.

2) Comment: HTTP binding: interpretation of arbitrary HTTP status
codes

Section 7.5.1.2 Requesting[2] describes how a SOAP sender reacts to
HTTP status codes returned by a SOAP receiver.

Table 17[3] only lists a limited number of methods for which next
states are listed. This seems to be contrary to the robustness
principle cited in Part 1[4]. What would happen if the requesting SOAP
node was receiving a 402 Payment Required[5] for example?

Regards,

Hugo

  1. http://www.w3.org/TR/2002/WD-soap12-part2-20020626/
  2. http://www.w3.org/TR/2002/WD-soap12-part2-20020626/#http-reqbindwaitstate
  3. http://www.w3.org/TR/2002/WD-soap12-part2-20020626/#tabreqstatereqtrans
  4. http://www.w3.org/TR/2002/WD-soap12-part1-20020626/#RFC1123
  5. http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.3
-- 
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/ - tel:+1-617-452-2092

Received on Wednesday, 3 July 2002 15:29:31 UTC