Self-hosted WebSocket server

Jan 17, 2014 at 11:47 AM
Hi,

I am looking for the way of having a self-hosted WebSocket server in a windows service. I know that it is possible because SignalR can, and it uses OWIN. For this particular project, we do not need all the SignalR infrastructure, we only need a plain and straightforward API for allow browsers to open a WebSocket and control when it connects/disconnects.

I have been taking a look at "Microsoft.Owin.Host.HttpListener.Tests.OwinWebSocketTests", but I am a little bit lost.

What would be the right way of selfhost a WebSocket server with OWIN?

Thanks.
Coordinator
Jan 17, 2014 at 4:05 PM
Feb 10, 2014 at 6:56 AM
I did as on the links, but still as a client connects ServerSentEvent. although it is I'm doing on Windows 8.
What are some other ideas?
Coordinator
Feb 10, 2014 at 6:41 PM
If you've removed SignalR from the client and server then why is anything attempting to do ServerSentEvent?

Can you get this plain sample server to talk to its sample client?
https://aspnet.codeplex.com/SourceControl/latest#Samples/Katana/WebSocketSample/WebSocketServer/Program.cs
https://aspnet.codeplex.com/SourceControl/latest#Samples/Katana/WebSocketSample/SampleClient/Program.cs

What client are you using?