The MIME Multipart/Interleaved and Application/Chunk Content-types
draft-herriot-multipart-interleaved-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Robert G. Herriot | ||
Last updated | 2001-03-29 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Multipart/Interleaved content-type, like the Multipart/Related content-type, provides a mechanism for representing objects that consist of multiple components. Each body part of a Multipart/Related entity represents a component, whereas each body part of a Multipart/Interleaved entity represents either a component or a part of a component. A body part that represents a part of a component has the content-type of Application/Chunk.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)