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

Document Type Expired Internet-Draft (individual)
Authors Wenbo Zhu  , Mike Jennings 
Last updated 2014-05-18 (latest revision 2013-11-14)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) 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-zhu-http-fullduplex-08.txt

Abstract

Full-duplex HTTP follows the basic HTTP request-response semantics but also allows the server to send response body to the client at the same time when the client is transmitting request body to the server. Requirements for full-duplex HTTP are under-specified in the existing HTTP (Hypertext Transfer Protocol -- HTTP/1.1) specification, and this memo intends to clarify the requirements of full-duplex HTTP on top of the basic HTTP protocol semantics.

Authors

Wenbo Zhu (wenboz@google.com)
Mike Jennings (mike.c.jennings@gmail.com)

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