[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Feedback on the MSS draft - content questions
Steve,
Again, thanks for taking the time to provide us with valuable
feedback. My thoughts below avec <cbf/>.
Chris
Steve Hole wrote:
>
> 1. Under what circumstances would an empty payload container be
> provided? What value would a "naked" header section have? A good
> example for this would help a lot.
<cbf>
An acknowledgment message would have no payload since the semantics
are embodied in the Header document itself (MessageType="Acknowledgment"
and RefToMessageId element value).
</cbf>
>
> 2. Can the payload part be a multipart/mixed or must it be one of the
> atomic parts? I can certainly imagine scenarious where the payload
> refers to other parts, and I see implications of this in the
> document, but it seems to me that it should be very explicit. In
> fact, I would give an example of both a single (atomic) part and one
> or more structured parts -- say an multipart/mixed and a
> message/rfc822.
<cbf>
As in my previous response, the payload is a single MIME object which
MAY be of any valid MIME type including multipart/*.
</cbf>
>
> ---
> Steve Hole
> Messaging Direct
> Mailto:Steve.Hole@MessagingDirect.com
> Phone: 780-424-4922
--
_/_/_/_/ _/ _/ _/ _/ Christopher Ferris - Enterprise Architect
_/ _/ _/ _/_/ _/ Phone: 781-442-3063 or x23063
_/_/_/_/ _/ _/ _/ _/ _/ Email: chris.ferris@East.Sun.COM
_/ _/ _/ _/ _/_/ Sun Microsystems, Mailstop: UBUR03-313
_/_/_/_/ _/_/_/ _/ _/ 1 Network Drive Burlington, MA 01803-0903
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC