@alex Most TCP protocols have a client/server nature. The client connects, sends a request to the server, the server sometimes changes some internal state, then sends a response to the client. Even HTTP allows a connection to remain open after that, for sending further commands. Other than the initial request to connect and go to WebSocket mode, WebSockets have no concept of client and server. Each participant sends stuff, and the other reads and acts on it, sometimes sending something back.