socket.io vs. SignalR
azure, signalr, socket.io
Solution
I'd have to say that SignalR is definitely the best approach for your application. With the current build our laptops serving as servers are pushing around 350k messages/s. With the next release it will be even higher (several multiples higher judging by current tests).
Check out the main site: http://signalr.net/
The GitHub: https://github.com/SignalR/SignalR
JabbR for questions: http://jabbr.net/#/rooms/signalr
Problem
I am developing a ASP.NET MVC app deployed on Azure, and looking for a library providing asynchronous transport mechanism/fallback. After my own research, I've concluded that there are two well-known candidates - Socket.io and SignalR. My question is simple) What's the pros and cons of them? It there any good reason to use one over the other? thanks :)