An overview of the
This series is the Chinese translation of the RFC6455 WebSocket protocol. The original intention of translating related document specifications is to have a deeper understanding of WebSocket and related content.
This article focuses on the WebSocket protocol
- Abstract
The specific content of the article is limited, and relevant chapters will be updated successively in the future. Interested students can continue to pay attention to it.
The translation version contains some personal understanding, most of the content is literal translation, and other parts of the content may be free translation, suitable for interested students to understand and learn. If you want to have a detailed understanding of the WebSocket protocol, you are advised to read the English documentation. If there are translation mistakes, you are also welcome to point out.
PS: I stopped blogging for a week because I had surgery for a broken hand. Has been discharged from hospital and will resume weekly updates.
Abstract
The WebSocket protocol enables bidirectional communication between a client running untrusted code in a controlled environment and a remote host that has chosen to communicate based on that untrusted code. This security model for WebSocket is the Origin-based security model used by reusable Web browsers (see here). This protocol consists of an open handshake process followed by basic data frames based on TCP. The goal of this technique is to provide a mechanism for browser-based applications to have two-way traffic with servers, without the need for multiple HTTP connections (for example, using XMLHttpRequest or Iframe to simulate long polling).
Memo status
This is an Internet standards tracking document.
This document is produced by the Internet Engineering Task Force (IETF). It represents the consensus of the Internet Engineering Task Force community. This document has been put out for public comment and approved for release by the IESG (Internet Engineering Steering Group). More information about Internet standards can be found in section 2 of RFC 5741.
Information and errata on the current state of this document, and how to give feedback, can be viewed here.
Copyright statement
Authorizing IETF credits and persons considered to be document authors in 2011. All rights reserved.
This document applies to BCP 78 and all relevant IETF documents prior to the RELEASE date of this document. Please read these documents carefully. They state your rights and limitations with respect to this document. The code component extracted from this document must contain the simplified BSD license agreement text required by law as described in Section 4.