wasmws
websocket
wasmws | websocket | |
---|---|---|
5 | 44 | |
61 | 18,557 | |
- | - | |
0.0 | 5.3 | |
over 2 years ago | over 1 year ago | |
Go | Go | |
Mozilla Public License 2.0 | BSD 2-clause "Simplified" 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.
wasmws
-
Is there an alternative to gorilla websocket?
Thanks for writing this! I found it really great to use when I wrote https://github.com/tarndt/wasmws
-
Goomerang 🪃 A protocol buffers over websockets communications library
Before looking at the readme, I thought this was an alternative to using https://github.com/tarndt/wasmws which lets you use gRPC over websockets so that you can use gPRC via WASM without needing an http to gRPC gateway. Now I'm understanding a bit differently. It looks like this uses protobufs but doesn't have anything to do with gRPC at all, instead implementing some of the communication parts of gRPC while ignoring the generation of services but instead focusing a bit more on message routing and pub/sub that you would probably still need NATS.io for if you were using gRPC.
-
Even More Minor Features in Go 1.18
The hijacking a websocket works very well, live in the future today! https://github.com/tarndt/wasmws
-
Migrating from nodejs to go codebase using gopherjs
Everything said above is valid, but if you do think you have a need to transpile... consider running any Go frontend code as WASM rather than Javascript. A few years ago I started doing my frontends and backends all in Go and its been wonderful. I even wrote a library so I could use gRPC from my WASM/Go frontends rather than REST: https://github.com/tarndt/wasmws . Extra wonderful, at least for my tastes. Once caveat is if your brotli compressed, CDN/browser cached, etagged Go WASM is still to big, you can usually make it even smaller by using tinygo rather than the std tool chain for the compiling to WASM.
-
Go and gRPC is just so intuitive. Here's a detailed full-stack flow with gRPC-Web, Go and React. Also, there is a medium story focused on explaining how such a setup might boost efficiency and the step-by-step implementation.
A while back I was writing a pure Go frontend app (WASM) and I wrote this so I could use gRPC rather than REST to talk to my backend: https://github.com/tarndt/wasmws
websocket
-
Websocket memory usage
What I can say is that if you will use Gorilla Websocket (https://github.com/gorilla/websocket) (it's archived now unfortunately, but still super robust) - then you can go to sth like 15-20kb per connection - see https://github.com/FZambia/go_websocket_memory - to achieve this you need to reduce read buffer size, reuse write buffers, use goroutine after hijacking connection (following chat example in Gorilla WebSocket repo).
-
Is there an alternative to gorilla websocket?
No Bugs? https://github.com/gorilla/websocket/issues Even if that were true at the time of stoping development, "No bugs" is something that can never be said for any software. I really wish this community stopped recomending to use abandoned libraries if only for the potential Security issues. A not maintained Library is a very lucrative target for vulnerability hunting.
- As gorilla websocket has been archived which library can we use?
-
gorilla fork
The Gorilla WebSocket License says:
-
WebSockets in Go: A hijackers' perspective
We'll be using WebSocket library: "github.com/gorilla/websocket" ❣️
-
How to install gorilla websocket in go 1.20?
package github.com/gorilla/websocket is not a main package
-
Polygon: Json Database System designed to run on small servers (as low as 16MB) and still be fast and flexible.
As for Websockets, (https://github.com/gorilla/websocket) it uses ws.NextReader() to handle heavy loads of connections.
- Best way for broadcast message un websocket
-
Gorilla/websocket or Melody?
I'm looking to build a game server that uses web sockets to communicate with clients, I've looked into some of the libraries and the main ones seem to be gorilla websockets and melody.
-
this code always comes back as Not found. in ubuntu 22
If this is what your import looks like "github.com/gorilla/websocket" that's wrong it should be just "github.com/gorilla/websocket"
What are some alternatives?
goomerang - A small communications library based on protocol buffers over websockets
Fiber - ⚡️ Express inspired web framework written in Go
wombat - Cross platform gRPC client
go-socket.io - socket.io library for golang, a realtime application framework.
grpc-web - gRPC for Web Clients
Mercure - 🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications
goja - ECMAScript/JavaScript engine in pure Go
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
ws - Tiny WebSocket library for Go.
chi - lightweight, idiomatic and composable router for building Go HTTP services
ote - ote updates a packages' go.mod file with a comment next to all dependencies that are test dependencies; identifying them as such.
Centrifugo - Scalable real-time messaging server in a language-agnostic way. Self-hosted alternative to Pubnub, Pusher, Ably. Set up once and forever.