websocket-client VS Websocket-Sharp

Compare websocket-client vs Websocket-Sharp and see what are their differences.

Websocket-Sharp

A C# implementation of the WebSocket protocol client and server (by sta)
Our great sponsors
  • talent.io - Download talent.io’s Tech Salary Report
  • Scout APM - Less time debugging, more time building
  • SonarQube - Static code analysis for 29 languages.
websocket-client Websocket-Sharp
2 2
3,061 4,786
1.8% -
7.1 9.8
8 days ago 9 days ago
Python C#
Apache License 2.0 MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

websocket-client

Posts with mentions or reviews of websocket-client. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-04-25.
  • Sending data to django channels groups via django views
    3 projects | reddit.com/r/codehunter | 25 Apr 2022
    EDIT: I could send the message using the websocket-client from the view
  • Everything about APIs
    11 projects | dev.to | 7 May 2021
    Websockets are (usually) for server to browser communication. The server hosts a WebSocket server, and clients can open a connection to that server. This is popular now mostly because it is faster and less resource-hogging than older ways of solving the problem, like long-polling/COMET. It is possible to connect 2 servers using websockets, but that is not usually what they are used for.

Websocket-Sharp

Posts with mentions or reviews of Websocket-Sharp. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-02-11.
  • 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?

When comparing websocket-client and Websocket-Sharp you can also consider the following projects:

SignalR - Incredibly simple real-time web for .NET

WebSocket4NET - A popular .NET WebSocket Client

SuperSocket - SuperSocket is a light weight, cross platform and extensible socket server application framework.

Fleck - C# Websocket Implementation

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.

WampSharp - A C# implementation of WAMP (The Web Application Messaging Protocol)

Akka.net - Port of Akka actors for .NET

awesome-grpc - A curated list of useful resources for gRPC

gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)