Support keep-alive pings in WebSocketGraphQlClient #608
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.
Added a keepalive option to the WebSocketGraphQlClient builder. This gets passed down to the WebSocketGraphQlTransport which then sends graphql ping messages over the websocket every keepalive seconds.
I've added basic handling to accept the pong messages back, but no processing or checks that a pong response is received in a timely manner, similar to the graphql-ws client library.