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

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

From: Doug Davis <dug@us.ibm.com>
Date: Fri, 15 Jun 2001 06:57:53 -0400
To: "Jean-Jacques Moreau" <moreau@crf.canon.fr>
Cc: jerry_liu@exch.labs.agilent.com, xml-dist-app@w3.org
Message-ID: <OFF73C457A.5EBD2710-ON85256A6C.003C2E96@raleigh.ibm.com >
Nope, in fact one of the interesting things about the SOAP spec
is that it doesn't actually say that the Body is where the 'real'
data is.  There is nothing stopping people from putting all of
the 'real' data in headers and the body could just be meta-data.
People just assume that it's the other way around, but the spec
is wide open on this.

"Jean-Jacques Moreau" <moreau@crf.canon.fr>@w3.org on 06/15/2001 03:45:11

Sent by:  xml-dist-app-request@w3.org

To:   jerry_liu@exch.labs.agilent.com
cc:   xml-dist-app@w3.org
Subject:  Re: Multiple SOAP messages in a single MIME multipart message?

Hi Jerry,

Maybe another solution would be to use multiple headers?

Anyone thinking this violates the spec?


jerry_liu@exch.labs.agilent.com wrote:

> [...] 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
> 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
> to send mutliple SOAP envelopes.  Seems much cleaner and elegant to do it
> this way. [...]
Received on Friday, 15 June 2001 06:59:26 UTC

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