Menu
Based on my understanding, the old SignalR repository is dead: there were no commits for a year (ironically, the guys who previously committed to it, now commit to Node,js), dozens of issues without response (we experienced a bug and had to downgrade to a version that's two years old).
There's a SignalR-Server repository which is a part of ASP.NET. It was supposed to be released with ASP.NET 5 (Q1 2016) but according to roadmap, it will be released later (Q3 2016). So I guess this is the repository where the actual SignalR development is going on. But the appropriate client repository is empty. So should I use the client from the old repository and a server from the new one? That's extremely confusing.
430
SignalR handles connection management automatically, and lets you broadcast messages to all connected clients simultaneously, like a chat room. You can also send messages to specific clients.
A SignalR app can scale out based on the number of messages sent, while the Azure SignalR Service scales to handle any number of connections.
SignalR provides two built-in hub protocols: a text protocol based on JSON and a binary protocol based on MessagePack. MessagePack generally creates smaller messages compared to JSON. Older browsers must support XHR level 2 to provide MessagePack protocol support.
In the default mode, the app server creates five server connections with Azure SignalR Service. The app server uses the Azure SignalR Service SDK by default. In the following performance test results, server connections are increased to 15 (or more for broadcasting and sending a message to a big group).
There will be a version 3 of signalR included in ASP.NET 5. The development team aim for a release by mid-2016. See this roadmap
mid-year 2018 (see ASP.NET Blog)
113
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
