The graphql-ws subprotocol (aka the graphql-transport-ws package) has been deprecated

[DoctorJohn]

The graphql-ws protocol has been deprecated in March and the corresponding graphql-transport-ws repository has been archived by its maintainers. They recommend using the graphql-transport-ws subprotocol which lives in the graphql-ws repository and is actively maintained.

The question is (for how long) do we want to keep supporting that protocol?

Some random thoughts:

• The old protocols specification leaves a lot of room for interpretation and a few edge cases are not addressed at all.
• Removing the old protocol would simplify websocket subprotocol selection.
• It could also simplify the GraphiQL template, that is until we decide to add support for subscriptions via server sent events ;)
• The Apollo GraphQL docs recommend the new protocol.
• The Relay docs have instructions for both protocols but they prefer the new one.
• Both the old and the new npm packages still have about the same amount of weekly downloads

[patrick91]

Both the old and the new npm packages still have about the same amount of weekly downloads

Shall we wait until this changes quite a bit? I'd love to remove code, but I also want to allow people to update to latest versions of strawberry, if we remove the support for it then it will be harder.

I guess we can mark the old protocol as deprecated for now?

Another option might be to move the old protocol stuff to a new package, but I don't know if that's easy to do