Persistent HTTP Connections
draft-ietf-http-ses-ext-01
| Document | Type |
Expired Internet-Draft
(http WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Alex Hopmann | ||
| Last updated | 1996-02-21 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
HTTP was designed to be an extremely lightweight stateless protocol based on TCP. However actual implementation experience suggests that the overhead inherent in establishing a separate TCP connection for every request represents a significant performance problem. This proposal suggests an optional facility for HTTP version 1.1 which allows a client to create persistent connections with a server. This facility is also designed to work with proxy servers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)