|10 days ago||16 days ago|
|GNU General Public License v3.0 or later||MIT License|
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
We haven't tracked posts mentioning SignalR yet.
Tracking mentions began in Dec 2020.
Recommended package for Interprocess communication?
3 projects | reddit.com/r/dotnet | 11 Feb 2021
I’m surprised no one mentioned web sockets. They’re extremely easy to get started with and you can have a full bi-directional communication in no time. I think there’s a native solution, but we’ve been using (WebSocketSharp)[https://github.com/sta/websocket-sharp] for a few years and it’s really simple to get started / gives good results for some heavy network communications as well.
What are some alternatives?
WebSocket4NET - A popular .NET WebSocket Client
SuperSocket - SuperSocket is a light weight, cross platform and extensible socket server application framework.
Fleck - C# Websocket Implementation
WampSharp - A C# implementation of WAMP (The Web Application Messaging Protocol)
unity-websocket-server - A simple, zero-dependency WebSocket server for Unity.
Websocket.Client - 🔧 .NET/C# websocket client library
NetGain - A high performance websocket server library powering Stack Overflow.