Communication Protocol¶
Clients and servers of STRIX send and receive data in units called messages. The messages are carried by lower layer communication protocols, among which you can choose one based on your needs.
Strix Cloud supports the following two communication protocols:
TCP |
The default communication protocol of STRIX. Usually TCP is recommended for use. |
WSS (Secure WebSocket) |
A web-friendly communication protocol. In Strix Cloud, you will use it together with Strix Unity SDK’s WebGL platforms (HTML5 clients) support. Strix Unreal SDK doesn’t support WSS. |
Note
Although STRIX servers also support UDP (RUDP) and regular WebSocket (WS), they are not available for the server instances in Strix Cloud.
See an article in Strix Unity SDK User’s Guide for the WebGL platform support in Strix Unity SDK.
You specify one of these communication protocols by the Protocol dropdown on the Creating a Cluster or Configuring Servers screens.
Note
The Protocol dropdown is visible only if the Strix server version is set to 1.3.0 or later. Earlier versions always use TCP.
The Protocol dropdown is initially hidden on the Create Cluster popup. You need to click on the Show more options to see it. See Creating a Cluster for details.
All server instances in a same application should be configured to use a same communication protocol.
Specifying a protocol in clients¶
For a client to use STRIX functions, it first requires connecting to a master server. The client needs to know the protocol used by the master server beforehand.
The client then connects to a room server. When connecting to a room server, the master server tells the protocol of the room server together with other properties such as an address of the room server. The client doesn’t need to know the protocol used by the room server previously.
See the documentation for an appropriate client SDK for detailed steps a client connects to servers.