websocket-client VS Websocket-Sharp

One other significant improvement in RoonCommandLine is an upgrade to the latest WebSocket client library.

EDIT: I could send the message using the websocket-client from the view

Websockets are (usually) for server to browser communication. The server hosts a WebSocket server, and clients can open a connection to that server. This is popular now mostly because it is faster and less resource-hogging than older ways of solving the problem, like long-polling/COMET. It is possible to connect 2 servers using websockets, but that is not usually what they are used for.

In fact, the default callback simply return true for all certificates (thus not validating the certificate at all; as documented).

Would it be better to write my own server using System.Net.WebSockets ? I've also looked into using websocket libraries like websocket-sharp

I’m surprised no one mentioned web sockets. They’re extremely easy to get started with and you can have a full bi-directional communication in no time. I think there’s a native solution, but we’ve been using (WebSocketSharp)[https://github.com/sta/websocket-sharp] for a few years and it’s really simple to get started / gives good results for some heavy network communications as well.