HTML5 WebSockets Client for .NET.

Question

So, I found this amazing thing called HTML5 WebSockets, the new API. This is still in the DRAFT version, but pretty well supported. Full duplex bidirectional communication. I know how to use it with JavaScript, there is an API. But if I want to use the WebSocket client in my C # /. NET application, how do I do this?

For example, JavaScript: http://bohuco.net/blog/2010/07/html5-websockets-example/

Are there any special client libraries for WebSockets in .NET?

Answer 1

sir SuperWebSocket includes a WebSocket server implementation and a WebSocket client implementation. SuperWebSocket Project Page

Answer 2

I recently did some research on this process by creating the .NET and Silverlight client library for Pusher . I found the following client libraries and WebSocket projects:

• Microsoft WebSocket Client Protocol
• SuperWebSocket Note: there is a client there, just find
• WebSocket-Sharp
• Anaida

At the moment, the Microsoft implementation is probably the easiest to use, and it also has a Silverlight library. SuperWebSockets has a Silverlight project in source, but not in the last drop.

Answer 3

Starting with .NET 4.5, WebSocket clients are supported through System.Net.WebSockets.ClientWebSocket

You can view or download the sample C # application from the MSDN code website: http://code.msdn.microsoft.com/WebSockets-middle-tier-5b2972ce/sourcecode .

In the questionnaire, sampling is mainly focused on connecting to WebSocket services, which is another important use case for a C # network application.

Answer 4

You better try WebSocket4Net: http://websocket4net.codeplex.com/

Answer 5

I have not tried the Microsoft implementation, but I think Xsockets has the fastest installation time (nuget package). Less than 3 minutes from start to launch full socketserver + client (demo chat application). Youtube demo

It has a backup of Silverlight and flash for older browsers.

Answer 6

You can use http://www.nuget.org/packages/Microsoft.AspNet.SignalR/ or http://www.asp.net/signalr

ASP.NET SignalR is a new library for ASP.NET developers that simplifies the development of web functions in real time. SignalR allows bidirectional communication between the server and the party. Servers can now redirect content to client access instantly when it becomes available. SignalR supports web sockets and is returning to other compatible technologies for older browsers. SignalR includes an API for managing connections (for example, connecting and disconnecting events), grouping connections, and authorization.

Answer 7

A friend and I just released a very light, lean, scalable C # web server server: https://github.com/Olivine-Labs/Alchemy-Websockets

We built it for use in our online game, so our main goal was to quickly and efficiently manage multiple connections. This is from my research, most effective there. And, as a bonus, it supports flash networks as a reserve for users without browsers with websocket support.

Answer 8

If you're looking for a high-performance enterprise WebSocket server, check out Kaazing . Kaazing has full .NET support, including Xamarin.

The following is a step-by-step guide for AMQP: Checklist: Creating Microsoft.NET AMQP Clients .

[Disclosure: I work for Kaazing.]

Answer 9

Yes, you will need a mediation server that supports the WebSocket protocol . This server can be written in any language, including .NET. Here is one for .NET, but it really can be any language. As for your site, it could be ASP.NET and the client side in javascript, which will talk to the WebSocket server.

Answer 10

I am deploying XSockets.net. The structure works well, it is supported, the developers offer paid support, but for normal problems, they are also quite active here in SO, and they help a lot.

They offer a .net API for socket implementations, as well as a javascript API for the client.

As a summary, I can recommend it.

Answer 11

You have several options.

• Roll your own - the specification is pretty simple
• Use a different experimental version, such as a C # web socket server
• Look at the MS WCF approach