The WebSocket protocol
draft-abarth-thewebsocketprotocol-01

Document Type Expired Internet-Draft (individual)
Last updated 2011-01-09
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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-abarth-thewebsocketprotocol-01.txt

Abstract

The WebSocket protocol enables two-way communication between a user agent running untrusted code running in a controlled environment to a remote host that has opted-in to communications from that code. The security model used for this is the Origin-based security model commonly used by Web browsers. The protocol consists of an initial handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g. using XMLHttpRequest or <iframe>s and long polling). Please send feedback to the hybi@ietf.org mailing list.

Authors

Ian Fette (ifette+ietf@google.com)
Adam Barth (ietf@adambarth.com)

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