Everything you need to know for SignalR for Web Pages is summarized at:
- Here is a maturing version of SignalR for Node.JS:
The APIs are really simple. It is a case of understanding your user account, room information, and message structure. After that, its all in figuring your use cases.
- Do we persist messages
- Are rooms (groups) persistable
- Can users accumulate offline messages
- Who can join?
- What rooms can they join?
- How much detail is in a message, and what is the message structure.
- Plain text
- Does the server need to sanitize the message?
- Are messages simple posts, or complex structures
So why SignalR rather than WebSockets? Because WebSockets don’t exist on all browsers yet. SignalR uses existing technology to overcome that limitation, until the day comes that everyone can use WebSockets.
Note: I don’t believe in the “versus” discussions on WebSockets + node.js vs SignalR + C#. This is silly. My ideal environment would be to make it so I can support Node.JS or C# hosts, and SignalR clients that can handle WebSockets. That way I can cover the widest range of compatibility without being married to one platform.