Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

WebSocket is a protocol that enables bidirectional communication over a single TCP connection. The protocol is designed to be implemented in web browsers and web servers, but it can be used by any client or server application. The WebSocket protocol is an independent TCP-based protocol and the only relation to HTTP is that the handshake is done as an HTTP upgrade request. The WebSocket protocol makes it easier to send real-time data to and from the server by enabling content to be sent to the client without the client having to make a request.

Deprecation

Netty version 3 will be deprecated in a future version of .

To mix agents with different Netty versions within the same execution context is not supported. Furthermore, you cannot run several execution contexts with different versions of Netty communicating with one another.

In there are both a Websocket Server agent, and a Websocket Client agent. These are collection agents for real-time workflows. Shown below are two workflows using the Websocket Server and Websocket Client.

Websocket Server workflow

Websocket Client workflow

Supported Protocol Specification

The WebSocket protocol has been implemented according to RFC 6455.

Prerequisites

The reader of this information should be familiar with:

  • TCP protocol

  • HTTP protocol

  • WebSocket protocol, RFC 6455


The section contains the following subsections:


  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.