I've been using this one w/o issue and at scale as well;
https://github.com/nhooyr/websocket
It also supports wasm.
On Mon, Dec 12, 2022, 1:22 PM Robert Engels wrote:
> I personally like minimal packages like this. Makes them easier to
> tailor/debug if something goes wrong. Also simpler to ta
I personally like minimal packages like this. Makes them easier to tailor/debug
if something goes wrong. Also simpler to take ownership/fork if needed - than a
package with a ton of code.
> On Dec 12, 2022, at 3:14 PM, Amnon wrote:
>
> By stdlib, you presumably mean the x/net/websocket packa
By stdlib, you presumably mean the x/net/websocket package, which is simple
ad has a clean API.
But it is also frozen, and has not been updated for 6 years.
Its docs begin with a deprecation notice:
// This package currently lacks some features found in alternative
// and more actively maintaine
You can use the stdlib websocket. See
https://github.com/robaho/go-trader/blob/master/internal/exchange/webserver.go
for an example.
> On Dec 12, 2022, at 12:57 PM, Amnon wrote:
>
> Which websocket implementation would people recommend for a new project,
> now that gorilla/websocket has been
Which websocket implementation would people recommend for a new project,
now that gorilla/websocket has been archived?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
