The WebSocket Protocol as a Transport for the Remote Framebuffer Protocol (RFB)
draft-garnero-rfb-websocket-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Pierre Garnero | ||
| Last updated | 2013-12-31 (Latest revision 2013-06-29) | ||
| 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 WebSocket protocol enables two-way realtime communication between clients and servers in web-based applications. This document specifies a WebSocket sub-protocol as a reliable transport mechanism between RFB (Remote Framebuffer Protocol) entities to enable usage of RFB in web-oriented deployments.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)