Bundled HTTP Exchanges
draft-yasskin-wpack-bundled-exchanges-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2018-12-15 (latest revision 2018-06-13) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-yasskin-wpack-bundled-exchanges-00.txt
https://www.ietf.org/archive/id/draft-yasskin-wpack-bundled-exchanges-00.txt
Abstract
Bundled exchanges provide a way to bundle up groups of HTTP request+response pairs to transmit or store them together. They can include multiple top-level resources with one identified as the default by a manifest, provide random access to their component exchanges, and efficiently store 8-bit resources.
Authors
Jeffrey Yasskin (jyasskin@chromium.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)