Skip to main content

Implications of Full-Duplex HTTP
draft-zhu-http-fullduplex-04

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
Authors Wenbo Zhu , Mike Jennings
Last updated 2012-05-20 (Latest revision 2011-11-17)
RFC stream (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

Full-duplex HTTP follows the basic HTTP request-response semantics but also allows the server to send response data to the client when the client is still transmitting request body to the server. Requirements for Full-duplex HTTP are under-specified in the existing HTTP specification [RFC2616], and this memo intends to clarify the requirements for implementing Full-duplex HTTP on top of the standard HTTP protocol.

Authors

Wenbo Zhu
Mike Jennings

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