Design Space for Bidirectional protocols
draft-loreto-design-space-bidirectional-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Salvatore Loreto , Peter Saint-Andre , Greg Wilkins , Stefano Salsano | ||
| Last updated | 2009-10-19 | ||
| 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
As technologies that enable bidirectional communication over HTTP have become more pervasive, interest has grown in (1) defining improved mechanisms for support of existing technologies (short-term solutions such as new HTTP headers) and (2) laying the foundation for development of new bidirectional protocols (long-term solutions such as WebSocket, Bidirectional Web Transfer Protocol, and Reverse HTTP). In order to provide context for such work, this document provides a first tentative map of the design space for bidirectional HTTP, with special attention to deployed infrastructure (e.g. web clients, intermediaries, firewalls, NATs, web servers) and programming environments.
Authors
Salvatore Loreto
Peter Saint-Andre
Greg Wilkins
Stefano Salsano
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)