Upgrading the 100-CONTINUE status for Broadcast in HTTP/1.1 Protocol
draft-bt-http-broadcast-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Raji Sankar | ||
Last updated | 2013-09-14 (Latest revision 2013-03-13) | ||
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 Hypertext Transfer Protocol -- HTTP/1.1 in RFC 2616 uses the 100-Continue status message with Expect: Continue header to send request body at a later time to the origin server. This memo explains how to extend this status message to send multiple responses from the origin server to the client for an extended period of time. This achieves the essential function of broadcast from the origin server to the client, without the client waiting for a response to a request.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)