Add subscriptions connection_init behaviour #597
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements a reply and
on_connect
handler to GQL_CONNECTION_INIT based on Apollo subscriptions transport ws ProtocolThis lets the client send a
connection_init
message with a custom payload to the server. The server handles this with aon_connect
closure.It replies
GQL_CONNECTION_ACK
if the connection is established andGQL_CONNECTION_ERROR
if refused (with an error provided byon_connect
).I'm a bit sceptical about the
#[allow(dead_code)]
I added, but I thought it may be useful to keeptype_name
in the structWsPayload
.An example to use this would be (based on this)
With an apollographql client one could use
as options for
apollo-link-ws
WebSocketLink
(see apollo docs).(for apollo server this would be: Apollo Server Websocket Authentification)