Examples of using The websocket protocol in English and their translations into Chinese
{-}
-
Political
-
Ecclesiastic
-
Programming
The WebSocket protocol is part of HTML5.
This is exactly what the WebSocket protocol delivers.
The WebSocket protocol was standardized in 2011.
Windows Azure WebSites has recently added support for the WebSocket protocol.
This is what the WebSocket Protocol provides.
To establish a WebSocket connection,the client and server upgrade from the HTTP protocol to the WebSocket protocol during their initial handshake.
Why the WebSocket protocol is the better choice.
Let's take a look at some of the ways in which you can use the WebSocket protocol without actually having to implement the protocol yourself.
The WebSocket protocol is not designed around request-response.
Thus, even if a given client uses the WebSocket protocol, it may not be possible to establish a connection.
The WebSocket protocol has two parts: handshake and data transfer.
In this article I will first show you how the WebSocket protocol works and explain its relationship to the larger TCP/IP suite.
The WebSocket protocol has been updated from version 7 to version 8.
This will be a wrapper that will handle the Websocket protocol details, so we only need to worry about exchanging data with the client.
The WebSocket protocol offers a persistent connection to exchange messages.
In WebSockets,this detail is left up to the messaging layer design. The WebSocket protocol offers no guarantee a message will be acknowledged in any form.
In fact, the WebSocket protocol is specifically designed to prevent any party from being duped into accepting a connection accidentally.
There's little doubt that JavaScript is the environment in which the WebSocket protocol will make the most impact, and the API is impressively simple.
The WebSocket protocol leaves these issues to the messaging layer design(which means there are no broad industry standards).
In 2011, RFC 6455- The WebSocket Protocol- was published to the IETF website.
The WebSocket Protocol Component API implements all of the protocol rules for handshaking and framing without ever actually creating a network connection of any kind.
In 2011, RFC 6455- The WebSocket Protocol- was published to the IETF website.
The WebSocket protocol uses the HTTP upgrade system(which is normally used for HTTP/SSL) to"upgrade" an HTTP connection to a WebSocket connection.
In 2011, RFC 6455- The WebSocket Protocol- was published to the IETF website.
The WebSocket protocol achieves this goal by masquerading as HTTP before switching to its own WebSocket data transfer on the same underlying TCP connection.
By default, the WebSocket Protocol uses port 80 for regular WebSocket connections and port 443 for WebSocket connections tunneled over Transport Layer Security(TLS)[RFC2818].
This is just what the WebSocket Protocol provides, and Dino Esposito explains how it's used and what it does.
IO primarily uses the WebSocket protocol with polling as a fallback option, while providing the same interface.
This piece of malware uses the WebSocket protocol for data communication, making it possible to exchange messages with the C&C server in real time.