[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Misunderstanding of SOAP message and protocol binding
And, IMO, doing a SOAP binding specification first will speed the
process of validating the details of the proposed standard and provide
an implementation that can be rapidly prototyped on a wide range of
equipment.
Larry
Chen, Weijing wrote:
I think in this mailing list there is a lot of confusion and
misunderstanding about SOAP. SOAP specification from W3C clearly separates
the specification into Message Construct and Underlying Protocol Binding
part. So far there is not solid evidence that why SOAP Message Construct
cannot be used for XMLCONF. Let's look a simple example using SOAP Message
Construct for "get-config":
<?xml version="1.0" ?>
<env:Envelope xmlns:env="http://www.w3.org/2001/09/soap-envelop";>
<env:Body>
<get-config
env:encodingStyle="http://www.w3.org/2001/09/soap-encoding";
xmlns="http://www.ietf.org/xmlconf";>
<target>
<running></running>
</target>
<test-option>test-then-set</test-option>
<write-option>replace</write-option>
<error-option>stop-on-error</error-option>
<config xmlns="http://example.com/schema/1.2/config";>
<interface name="Ethernet0/0">
<address>
<ipv4>1.2.3.4</ipv4>
<ipv4-mask>255.0.0.0</ipv4-mask>
</address>
</interface>
</config>
</get-config>
</env:Body>
</env:Envelope>
Now if someone wants put the above "get-config" message into said HTTP
binding, he can use HTTP POST:
POST /Reservations HTTP/1.1
HOST: noc1.serviceproviderA.com
Content-Type: application/soap+xml; charset="utf-8"
Content-length: nnnn
<and above message>
Or someone wants to use BEEP binding, he can use BEEP protocol, but with the
same SOAP Message Construct.
The SOAP Message Construct allows the about a dozen usage: fire-and-forget
to single reciever, fire-and-forget to multiple receivers, request/response,
rpc, request with acknowledgement, request with encrypted payload, third
party intermediary, conversational message exchange, message header and
payload encryption, communication via multiple intermediaries, asynchronous
messageing, send non-XML data, multiple asynchronous responses, incremental
parsing/processing of SOAP messages, event notification, caching, routing,
tracking, caching with expiration, quality of service, etc. Also the SOAP
fault and error processing is fairly comprehensive. An error code exmaple
is:
<?xml version='1.0' ?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope";
xmlns:xmlconf="http://www.ietf.org/2003/05/xmlconf";>
<env:Body>
<env:Fault>
<env:Code>
<env:Value>env:Sender</env:Value>
<env:Subcode>
<env:Value>xmlconf:BadArguments</env:Value>
</env:Subcode>
</env:Code>
<env:Reason>
<env:Text xml:lang="en-US">Processing error</env:Text>
<env:Text xml:lang="cs">Chyba zpracování</env:Text>
</env:Reason>
<env:Detail>
<e:myFaultDetails
xmlns:e="http://example.org/faults";>
<e:message>Name does not match card id</e:message>
<e:errorcode>999</e:errorcode>
</e:myFaultDetails>
</env:Detail>
</env:Fault>
</env:Body>
</env:Envelope>
So someone please tell me why SOAP Message Construct can be not reused
beside the reason of NIH syndrome.
--
Weijing Chen
SBC Technology Resources
9505 Arboretum Blvd.
Austin, TX 78759
512 372 5710
wchen@tri.sbc.com
--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>
--
Larry Menten Lucent Technologies/Bell Laboratories
Phone: 908 582-4467 600 Mountain Avenue, Murray Hill, NJ 07974 USA
--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>