Examples of using The websocket protocol in English and their translations into Chinese
{-}
-
Political
-
Ecclesiastic
-
Programming
This section describes some security considerations applicable to the WebSocket Protocol.
The WebSocket protocol has been standardized by the IETF as RFC 6455.
Additional header fields are used to select options in the WebSocket Protocol.
The WebSocket protocol has been standardized by the IETF as RFC 6455.
The WebSocket protocol has been updated from version 7 to version 8.
The WebSocket protocol was designed to work well with the existing Web infrastructure.
In the WebSocket Protocol, data is transmitted using a sequence of frames.
If the client is connected, we then need to perform the Websocket protocol handshake.
Unlike most of its predecessors, the WebSocket protocol was designed with security in mind.
The WebSocket protocol fits somewhat neatly into the TCP/IP suite above TCP and alongside HTTP.
(Note that masking is done whether or not the WebSocket Protocol is running over TLS.).
It's clear from studying the WebSocket protocol that it was designed after the Web insecurity apocalypse.
The WebSocket Protocol attempts to address the goals of existing bidirectional HTTP technologies in the context of the existing HTTP infrastructure;
To achieve compatibility, the WebSocket handshake uses the HTTP Upgrade header[1] to change from the HTTP protocol to the WebSocket protocol.
Header field in the client's handshake includes the version of the WebSocket Protocol with which the client is attempting to communicate.
NET and provides HttpListener- which is itself based on the native HTTP Server API used by IIS- to provide server support for the WebSocket protocol.
The WebSocket protocol was standardized in 2011 by the IETF as RFC 6455, and the WebSocket API in Web IDL is being standardized by the W3C.
Web-side alert real-time data using the WebSocket communication protocol, so the browser must support HTML5 to be able to use the system.
The WebSocket API, built on top of the IETF WebSocket protocol(RFC6455), offers a bidirectional, more flexible, and less resource intensive network connectivity than XMLHttpRequest.