How about using GameServer and WebGameClient by using HTTP3?

[laskdjlaskdj12]

When you streamed yesterday, you said you couldn't communicate UDP through a web browser, but I found the answer today. I found HTTP3 is UDP-based, and the latest Chrome supports it, so make a suggestion.

And found out, There are HTTP3 Websocket api, named by "Webtransport". Here's document for this.

https://chromestatus.com/feature/4854144902889472

[unitoftime]

Oh cool. I had no idea that feature was being introduced. I'll definitely track the development on this. It's obviously a big change, especially if there isn't a library that wraps the webtransport interface already. I'll have to dig into this some more.

Thanks for bringing it up though!

[unitoftime]

Saw this got closed. I ended up implementing webrtc which exposes UDP sockets in browser. It requires a little bit of weirdness to get it set up. I have a WIP implementation of how it looks here:
https://github.com/unitoftime/flow/blob/master/net/webrtc.go

I think if there becomes a more standardized way of dialing UDP sockets from browsers without having to do all the webrtc setup shenanigans I'll probably switch to that.

[laskdjlaskdj12]

Sorry Unit of time i've misclicked that close this issue :( Okay I'll let you know if I find something good after I see it.

[unitoftime]

All good. Not a problem!