Wasm compatibility of web socket

[gedw99]

If you changed from using gorilla to one of the wasm compatible web socket libs then people could use wasm plugins with your system.

Am talking about this:

https://github.com/anycable/anycable-go/blob/master/ws/handler.go#L13

There’s a few one out there that work with nats. Just ask if you’re curious.

then peopke can just write in any language and compile to wasm and tap into the nats stream over web sockets.

I use , python, typescript and golang . Python for ML , rust for perf etc .

Basically it makes things agnostic to the language .

[gedw99]

https://pkg.go.dev/nhooyr.io/websocket Works with wasm .

[gedw99]

Here is a nice analysis of scaling it out to a million concurrent users

https://centrifugal.github.io/centrifugo/blog/scaling_websocket/

[gedw99]

On a side note quic can also work well with nats .

multipathing so that when uses WAN changes it auto adapts is an awesome feature over web sockets.

seen many nats / quic systems work this way on the gateway level.

Would be just another transport like in the ws folder .

[palkan]

Thanks for the suggestions and the resources.

AFAICS, nhooyr.io/websocket only supports compiling WebSocket client code to WASM, which is not relevant to anycable-go.

Also, there are some technical limitations (such as no support for accessing the underlying socket, or fd) which are blocking us from using this library. For now, the only alternative to gorilla for us is gobwas/ws.