[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Use of MIME multipart for zero payload containers
According to the abstract, the spec says it defines a "binding or a SOAP 1.1 message to be carried within a MIME multipart/related." Later on it uses "one or more" to talk about attachments, but there's nothing that says an attachment is required. It uses language like "Referenced parts must..." so if they're not referenced, then they needn't. :) Personally, I think it's angels on pinheads. As Dale pointed out, the underlying MIME spec allows one-part multipart. There is nothing in the spec that says you can't use it. So go for it. But to be sure I sent email to the authors asking for clarification. I'm still in favor of always using one MIME format. /r$ PS: Recalling the IP issues when ebXML adopted SwA, I like this quote from the spec "In other words, we take a minimalist approach to show what is already possible with existing standards without inventing anything." :) -- Zolera Systems, Your Key to Online Integrity Securing Web services: XML, SOAP, Dig-sig, Encryption http://www.zolera.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC