Re: Use of MIME multipart for zero payload containers

[christopher ferris <chris.ferris@Sun.COM>]

It's always MIME. The media type is either multipart/related with
a type attribute of text/xml or it is text/xml. No sniffing required.

It should be noted that the issue of whether SOAP1.2 should adopt
application/xml, application/soap or application/soap+xml is currently
raging[1] again.

[1] http://lists.w3.org/Archives/Public/xml-dist-app/2001Sep/0085.html

Hopefully, we'll settle on application/soap or application/soap+xml;-)

Cheers,

Chris

Scott Hinkelman wrote:
> 
> There has always been that concern in my mind that if it is not always
> MIME, then your endpoint code may have to sniff the message to determine if
> it is pure SOAP or a MIME.    no?
> 
> Scott Hinkelman, Senior Software Engineer
> XML Industry Enablement
> IBM e-business Standards Strategy
> 512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
> srh@us.ibm.com, Fax: 512-838-1074
> 
> "Burdett, David" <david.burdett@commerceone.com> on 09/20/2001 09:04:59 AM
> 
> To:   "'Dan Weinreb'" <dlw@exceloncorp.com>, dmoberg@cyclonecommerce.com
> cc:   rsalz@zolera.com, "Burdett, David" <david.burdett@commerceone.com>,
>       chris.ferris@sun.com, david@drummondgroup.com,
>       ebxml-msg@lists.oasis-open.org
> Subject:  RE: Use of MIME multipart for zero payload containers
> 
> Can we have a firm proposal from one of our "SOAP experts" on what we
> should
> do to fix this issue as there seem to be several alternatives ...
> 
> Regards
> 
> David
> 
> -----Original Message-----
> From: Dan Weinreb [mailto:dlw@exceloncorp.com]
> Sent: Wednesday, September 19, 2001 2:10 PM
> To: dmoberg@cyclonecommerce.com
> Cc: rsalz@zolera.com; david.burdett@commerceone.com;
> chris.ferris@sun.com; david@drummondgroup.com;
> ebxml-msg@lists.oasis-open.org
> Subject: Re: Use of MIME multipart for zero payload containers
> 
>    Date: Wed, 19 Sep 2001 10:14:23 -0700
>    From: "Dale Moberg" <dmoberg@cyclonecommerce.com>
> 
>    The syntax, as I decipher it, requires one body-part but
>    zero or more encapsulations (which is what a second or nth
>    body part is called). So multiparts with just one part
>    are allowed.
> 
>    That does not settle what do in ebxml, but there is
>    nothing "wrong" with a multipart with one body part.
> 
> Yes, the MIME standard definitely allows multiparts with one part.
> What I'm saying is that SOAP 1.1 With Attachments doesn't say whether
> you're supposed to (a) use MIME multiparts with one part, or (b) go
> back to the original SOAP format and not use MIME multiparts at all.
> It would be better if it said, one way or the other.  And then ebXML
> MS would just "inherit" this.
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>