Menu
I have already created my server in System.Net.WebSockets and now after transferring it between machines I had noticed Windows Server 2008 is not supported, are there any other implemetations which support an X509Certificate as authentication and would require minimal conversation.
I have been googling for this in the past 2 hours but haven't found anything meaningful, just a collection of poorly written, poorly documented libraries that throw exceptions on the regular, specifically SuperSocket, the server implementation of which seems to be complete buggy bull.
Could anyone post some sample client code from a decent library? I am growing desperate.
834
Websockets are largely obsolete because nowadays, if you create a HTTP/2 fetch request, any existing keepalive connection to that server is used, so the overhead that pre-HTTP/2 XHR connections needed is lost and with it the advantage of Websockets.
There are several challenges you have to overcome because the WebSockets protocol is more CPU demanding on the client's side than on the server's side. At the same time you need a lot of RAM to store information about open connections if you have millions of them.
Avoid using WebSockets if only a small number of messages will be sent or if the messaging is very infrequent. Unless the client must quickly receive or act upon updates, maintaining the open connection may be an unnecessary waste of resources.
WebSockets is actually the underlying transport that SignalR uses, at least most of the time. SignalR has the ability to fall back to other ways of transporting messages, such as long-polling over HTTP. This is useful in situations where you don't have WebSockets support.
Frameworks include:
More options available via the realtime web tech guide
64
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
