Obtaining Connection Endpoint For UDP/RUDP, TCP, and WebSocket Connections

In order to establish a connection to interact with Diarkis server cluster you must obtain connection endpoint and other necessary data from it via HTTP API.

The diagram below describes the relations between the clients, Diarkis server cluster, and your application server(s).

List of items that Diarkis Server Cluster Includes:

  • Diarkis Server Cluster: HTTP, TCP, UDP/RUDP, and WebSocket servers (Pods)

  • Diarkis SDK: C# and C++ (Diarkis Client SDKs will be part of Client device applications)

What is “Application Server”:

Application server is not a part of Diarkis server cluster, but provided and maintained by the application.

How It Works

Diarkis does not have client authentication. This is because Diarkis does not manage user data.

When you start real-time communications using Diarkis, you must first authenticate the clients with your application server. The application server then requests connection a endpoint and encryption keys from Diarkis HTTP server directly and forward them to the authenticated clients.

Last updated