I currently have a TCP server application written in .Net that receives and submits messages to clients. I am looking at building a web application so need the communication layer.
I have built a Node.JS + Socket.IO app which connects to my TCP server and then pushes communication to the web application and all works fine.
I have just read about SignalR as an alternative to keep it in the .Net stack.
However I have also found that I could write a C# Websocket Server, a basic demo here
I assume that this basic server is what SignalR is but obviously with a lot more functionality in it?
What I'm trying to decide is do I just append my current TCP application with a Websocket server or do I go down a separate SignalR or Node.js route? Out of interest how does a SignalR application run, is it as a Windows service, console app or IIS service?
SignalR is like Socket.IO in that it supports transport negotiation/fallback. It is a framework and not a server, so you need to host it on a server of some sort. We have hosts for ASP.NET, OWIN (e.g. Kayak) and self-host, so you can run it in your own process easily, e.g. a Windows service.
SignalR has supported clients for browsers (JS), .NET, Windows Phone 7 and Silverlight. There are also contributed clients for things like iOS, Mono Touch, etc.
SignalR will give you a much higher level API than raw sockets which is its big advantage, allowing you to do things like "RPC" from server to clients in a broadcast (or targeted) fashion.
I've used both technologies and work on both sides of the .NET / node stacks.
Update - removed jquery info since it is no longer applicable