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

[Binary data] Application/Multiplexed content-type draft

From: Jean-Jacques Moreau <moreau@crf.canon.fr>
Date: Fri, 11 May 2001 11:43:09 +0200
Message-ID: <3AFBB42D.E1DEA467@crf.canon.fr>
To: "xml-dist-app@w3.org" <xml-dist-app@w3.org>
The following draft[1] might also be applicable to the transport of
binary/application data within an XMLP message.

Jean-Jacques.

   The Application/Multiplexed content-type, like the
Multipart/Related
   content-type, provides a mechanism for representing objects that
   consist of multiple components.  An Application/Multiplexed entity
   contains a sequence of chunks. Each chunk contains a MIME message
or
   a part of a MIME message. Each MIME message represents a component
of
   the compound object, just as a body part of a Multipart/Related
   entity represents a component. With an Application/Multiplexed
   entity, a body part and its reference in some other body part may
be
   separated by many octets -- more octets than a memory-constrained
   device can deal with. With an Application/Multiplexed entity, a
chunk
   can contain part of a message. This allows a message and its
   reference in some other message to be made quite close -- close
   enough for a memory-constrained device to deal with.  This document

   defines the Application/Multiplexed content-type. It also provides
   examples of its use.

[1]
http://search.ietf.org/internet-drafts/draft-herriot-application-multiplexed-00.txt
Received on Friday, 11 May 2001 05:44:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:01 GMT