Making HTTP Pipelining Usable on the Open Web
draft-nottingham-http-pipeline-01

Document Type Expired Internet-Draft (individual)
Last updated 2011-03-13
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized 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-nottingham-http-pipeline-01.txt

Abstract

Pipelining was added to HTTP/1.1 as a means of improving the performance of persistent connections in common cases. While it is deployed in some limited circumstances, it is not widely used by clients on the open Internet. This memo suggests some measures designed to make it more possible for clients to reliably and safely use HTTP pipelining in these situations.

Authors

Mark Nottingham (mnot@mnot.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)