W3C home > Mailing lists > Public > xml-dist-app@w3.org > June 2001

RE: Multiple SOAP messages in a single MIME multipart message?

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Fri, 15 Jun 2001 06:52:57 -0700
Message-ID: <79107D208BA38C45A4E45F62673A434D03441A0D@red-msg-07.redmond.corp.microsoft.com>
To: <jerry_liu@exch.labs.agilent.com>, <xml-dist-app@w3.org>
Cc: "Satish Thatte" <satisht@microsoft.com>

The SOAP attachment spec talks about how to embed a single SOAP message
within a MIME multipart/related message. If there are other SOAP
messages in the MIME multipart message then they are not "active" but
merely considered data. From [1]"

"A SOAP processor compliant with this specification that receives a SOAP
1.1 message carried in the root body part of a Multipart/Related MIME
message must process the SOAP message according to the rules for
processing SOAP 1.1 messages as defined by SOAP 1.1. In particular, a
SOAP processor that receives an invalid message must generate a Client
fault code as described in SOAP 1.1, section 4.4.1."

Also, the HTTP binding doesn't support this. In general, boxcarring
causes a lot of problems - especially with fault handling etc. If you
really want to use HTTP then the simplest and cleanest is to use
multiple HTTP requests. If you don't deal with the request right away
then use a 202 Accepted HTTP status code.

You might also want to have a look at DIME/SOAP-RP [2].

>I have a question regarding batching multiple SOAP messages.
>I'm using SOAP in combination with HTTP and the RPC 
>representation described in 1.1 spec.  I have a need to batch 
>multiple SOAP messages within a single HTTP request (or 
>response).  (Long story as to why but basically some of the 
>message receivers in the system are not always available and 
>we need to queue SOAP messages destined for them.)  I suppose 
>one way to do it is to just hide multiple RPC invocations 
>inside the one parent one, though that seems inelegant to me.  
>A method I like better is to just use MIME multipart to send 
>mutliple SOAP envelopes.  Seems much cleaner and elegant to do 
>it this way.
>My question is, does this scheme violate the "SOAP Messages 
>with Attachments" (http://www.w3.org/TR/SOAP-attachments) 
>spec?  Or am I only allowed one SOAP envelope per multipart 
>message?  Are there other ways of batching multiple SOAP 
>messages I hadn't thought of that would work also?


[1] http://www.w3.org/TR/SOAP-attachments#SOAPMultipart
[2] http://www.gotdotnet.com/team/xml_wsspecs/
Received on Friday, 15 June 2001 09:57:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:11:36 UTC