[go-nuts] Re: Which websockets implementation
gorrila/websocket is a very mature library. The current maintainer stepping down doesn't change that. I wouldn't avoid it. The very fact that its been so stable and successful for so long that there's nothing left to do on it is actually a recommendation. Nice tutorial: https://blog.markvincze.com/programmatically-refreshing-a-browser-tab-from-a-golang-application/ On Monday, December 12, 2022 at 12:57:19 PM UTC-6 Amnon wrote: > 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 to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/cdb789e5-0651-48a6-bf8c-d3d9f085fef0n%40googlegroups.com.
[go-nuts] Re: Which websockets implementation
> By stdlib, you presumably mean the x/net/websocket package, Careful with this library, it's not quite correct. Websocket is a frame-oriented protocol, while x/net/websocket implements a simplistic API that does not always preserve frame boundaries. Correct implementations include: https://github.com/gorilla/websocket https://github.com/nhooyr/websocket -- Juliusz -- 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 to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/87sfhaajyb.fsf%40pirx.irif.fr.
