Support for out-of-order responses in HTTP
draft-mogul-http-ooo-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jeffrey Mogul | ||
| Last updated | 2001-04-09 | ||
| 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 introduction of persistent connections and pipelining into HTTP has resulted in potential performance benefits, but has also exposed the problem of head-of-line blocking. A simple, compatible, and optional extension to HTTP to allow a server to issue responses out of order could significantly reduce HOL blocking. In this extension, clients add short ID fields to their requests, and servers echo these IDs back in their responses. This extension is defined as a hop-by-hop rather than end-to-end mechanism, so it avoids much of the complexity of the end-to-end approach.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)