Kaazing Websocket Gateway and Load-Balancing routers.
kaazingWebsocket网关与负载均衡路由器。
Encrypted WebSocket Connections and Explicit Proxy servers.
加密的WebSocket连接与显式的代理服务器。
Will proxy servers automatically kill WebSocket connections?
代理服务器是否会自动中断WebSocket连接？
Unencrypted WebSocket Connections and Explicit Proxy servers.
未加密WebSocket连接与显式代理服务器。
Encrypted WebSocket Connections and Transparent Proxy servers.
加密的WebSocket连接与透明的代理服务器。
Unencrypted WebSocket Connections and Transparent Proxy servers.
未加密的WebSocket连接与透明代理服务器。
The network traffic is made up of WebSocket frames and not HTTP requests and responses.
网络传输是由WebSocket frames构成的，而非HTTP请求与响应。
Future releases will also include the WebSocket protocol and a Comet protocol implementation.
将来的版本还会包含对WebSocket协议和Comet协议的实现。
After those handshakes succeed, WebSocket traffic can start flowing unimpeded through the proxy server.
这系列的握手成功后，WebSocket信息流就可以开始无阻碍的通过代理服务器了。
Additionally, I'll explain how Kaazing WebSocket Gateway and its Web Socket emulation can add additional value.
此外，我将会解释KazzingWebSocket网关及其WebSocket模仿功能如何带来额外的价值。
It all comes down to understanding the end-to-end network topology you are deploying your WebSocket application in.
所有都归结到要理解你所要部署WebSocket应用的端到端网络拓扑。
This means that the load-balancing router stays out of the way of the actual WebSocket traffic, thus reducing latency.
这意味着负载均衡路由器不介入真正的WebSocket流量，由此减少了延迟。
Therefore, a well-behaved transparent proxy server will cause the WebSocket upgrade handshake to fail almost immediately.
因此，一个工作良好的透明代理服务器几乎会立刻引起WebSocekt升级握手失败。
Once established, WebSocket data frames can be sent back and forth between the client and the server in full-duplex mode.
一旦连接建立，WebSocket数据帧就可以以全双工的模式在客户端和服务器之间来回传输。
Figure 2 shows how using unencrypted WebSocket connections are more likely to fail in all but the simplest network topologies.
图2显示了在几乎是最简单的网络拓扑中为什么使用未加密的WebSocket连接更容易失败。
A WebSocket server that is used in such a scenario must be added to the white list of servers for connections to be successful.
在这种场景中使用的WebSocket服务器必须被加入到服务器白名单中，连接才有可能成功。
Figure 2 shows the decisions that are made during the setup of a WebSocket connection between the browser and the WebSocket server.
图2展示了在浏览器与WebSocket服务器之间建立WebSocket连接过程中所做的决定。
In the future, however, proxy servers will likely become Web Sockets-aware and able to properly handle and forward WebSocket traffic.
然而，未来，代理服务器将会是WebSocket可知的，并且能够合理的处理与转发WebSocket信息流。
It introduces the WebSocket interface and defines a full-duplex communication channel that operates through a single socket over the Web.
它引入了WebSocket接口并且定义了一个全双工的通信通道，通过一个单一的套接字在Web上进行操作。
When the explicit proxy server allows the connect method, the TLS handshake is sent, followed by the WebSocket connection upgrade handshake.
当显式的代理服务器允许CONNECT方法时，TLS握手被发送出去，后面紧跟着WebSocket连接升级握手。
Apple has even implemented WebSocket in the latest release of iOS 4.2, while developers must wait for support in Windows Phone 7 and Android.
Apple甚至在最新发布的iOS 4.2中实现了WebSocket，而开发者则必须得等待WindowsPhone7和Android的支持。
When a proxy server forwards a request to the (WebSocket) server, it is expected to strip off certain headers, including the Connection header.
当代理服务器将请求转发到（WebSocket）服务器时，将会被剥去一些特定的消息头，包括Connection消息头。
It is even possible for proxy servers to have their own explicit proxy servers, increasing the number of hops the WebSocket traffic has to make.
代理服务器甚至还有可能有它们自己的显式的代理服务器，这又增加了WebSocket传输需要的中继数。
In the future, WebSocket gateways and servers may even be able to dynamically upgrade to Web Sockets Secure if an uncooperative proxy server is detected.
未来，WebSocket网关和服务器能够支持在探测到不合作的代理服务器时，动态地升级到WebSocket安全。
NOTE: This makes it harder for a script to perform a denial-of - service attack by just opening a large number of WebSocket connections to a remote host.
注意：这使得通过一个脚本向远程服务器打开大量的连接的方式进行“拒绝服务攻击”更困难。
We use Socket.IO, which abstracts over websockets and provides fallbacks to support websocket-style communication for browsers that don’t have websockets yet.
我们使用Socket.IO，它对WebSocket进行了抽象，还对尚没有WebSocket的浏览器提供了应变方案，以支持WebSocket式的通信。
Figure 1 shows a simplified network topology in which clients use a browser to access back-end TCP-based services using a full-duplex HTML5 WebSocket connection.
图1展示了一个简化的网络拓扑，客户端使用浏览器来访问后端基于TCP的服务，这里使用了全双工的HTML5WebSocket连接。
To establish a WebSocket connection, the client and server upgrade from the HTTP protocol to the Web Socket protocol during an initial handshake, as shown in Example 1.
要建立一个WebSocket连接，客户端和服务器在初次握手的时候从HTTP协议提升到WebSocket协议，如例1所展示的。
Kaazing WebSocket gateway is a highly optimized, proxy-aware WebSocket gateway, which provides native WebSocket support as well as Web Socket emulation for older browsers.
kaazingWebSocket网关是高度优化的，代理感知的WebSocket网关，提供原生的WebSocket支持和针对上一代浏览器的WebSocket模拟功能。
If a browser is configured to use an explicit proxy server then it will first issue an HTTP connect method to that proxy server while establishing the WebSocket connection.
如果一个浏览器被配置为使用显式的代理服务器，那么在建立WebSocket连接时它首先会向该代理服务器发出一个HTTPCONNECT方法。
应用推荐