Replies: 1 comment
-
Hey there! The graphql-ws/sse/http suite is about transports that are decided depending on your project's transport requirements.
You don't have to. There is no need to use WS for non-subscription GraphQL. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was looking for some docs on as to why this project exist.
https://the-guild.dev/graphql/ws
has recipes, a basic list of features and a spec section but it never mentions when would you use it?
What is the main usecase? I have always used a regular http transport with graphql in the past and websocket for subscriptions. Why would you want to go with ws transport instead of an http one?
Beta Was this translation helpful? Give feedback.
All reactions