RFC 3391: The MIME Application/Vnd.pwg-multiplexed Content-Type
In plain English — editorial summary, not part of the RFC
The Application/Vnd.pwg-multiplexed content-type, like the Multipart/Related content-type, provides a mechanism for representing objects that consist of multiple components. An Application/Vnd.pwg- 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 a Multipart/Related entity, a body part and its reference in some other body part may be separated by many octets. With an Application/Vnd.pwg-multiplexed entity, a message and its reference in some other message can be made quite close by chunking the message containing the reference. For example, if a long message contains references to images and the producer does not know of the need for each image until it generates the reference, then Application/Vnd.pwg-multiplexed allows the consumer to process the reference to the image and the image before it consumes the entire long message. This ability is important in printing and scanning applications. This document defines the Application/Vnd.pwg- multiplexed content-type. It also provides examples of its use.
Document record
- Document ID
- RFC3391
- Published
- December 2002
- Authors
- R. Herriot
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3003The audio/mpeg Media TypeCurrent
November 2000
- RFC 3362Real-time Facsimile (T.38) - image/t38 MIME Sub-type RegistrationCurrent
September 2002
- RFC 3023XML Media TypesObsoleted
January 2001
- RFC 2646The Text/Plain Format ParameterObsoleted
August 1999
- RFC 2480Gateways and MIME Security MultipartsCurrent
January 1999
- RFC 2423VPIM Voice Message MIME Sub-type RegistrationObsoleted
September 1998
- RFC 2397The "data" URL schemeCurrent
August 1998
- RFC 2388Returning Values from Forms: multipart/form-dataObsoleted
August 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?