How thought gorilla/websocket altanative plan

[S-H-GAMELINKS]

What happened?

Gorilla Web Toolkit was archived in few days ago. https://github.com/gorilla

Therefore, I thought that we may need to consider migrating to another library or fork gorrila/websocket in the future and created this issue.

What did you expect?

Currently, it is dependent on a specific Websocket implementation, and we think it would be good if we could mitigate this to some extent.

How about adding new structures or interfaces to allow for more flexible use of Websocket?

Minimal graphql.schema and models to reproduce

Nothig.

versions

Nothing.

[StevenACoffman]

Hi, It's possible someone will maintain a fork of gorilla, but probably not a rush. If not, there are a few alternatives:

• https://github.com/reugn/go-streams
• https://github.com/kataras/neffos

Another popularly used websocket library (although not as actively maintained):

• https://github.com/gobwas/ws

[S-H-GAMELINKS]

Thanks for comments. If so, there seems to be no need to rush into a response, etc. once it's done :)

FYI: I believe this Fork will continue to be maintained from what I have found. https://github.com/shiguredo/websocket

The only concern I have is that we will be communicating in Japanese :)

[it512]

nhooyr.io/websocket

[gdejong]

As of March 2023 https://github.com/gobwas/ws is being actively maintained again. See https://github.com/gobwas/ws/issues/162

[juddbaguio]

Might as well take a look at https://github.com/lesismal/nbio

[gdejong]

And as of July 2023 the Gorilla web toolkit project has a new group of Core Maintainers.

https://gorilla.github.io/blog/2023-07-17-project-status-update/