-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for client to send ping messages for subscriptions #605
Labels
status: superseded
Issue is superseded by another
Comments
spring-projects-issues
added
the
status: waiting-for-triage
An issue we've not yet triaged
label
Feb 5, 2023
toby200
added a commit
to toby200/spring-graphql
that referenced
this issue
Feb 8, 2023
toby200
added a commit
to toby200/spring-graphql
that referenced
this issue
Feb 8, 2023
toby200
added a commit
to toby200/spring-graphql
that referenced
this issue
Feb 8, 2023
I've raised a pull request to address this |
toby200
added a commit
to toby200/spring-graphql
that referenced
this issue
Feb 8, 2023
Thanks, I'll close this as superseded by the PR. We can continue the conversation there. |
rstoyanchev
added
status: superseded
Issue is superseded by another
and removed
status: waiting-for-triage
An issue we've not yet triaged
labels
Feb 9, 2023
@rstoyanchev May I know the maven dependency that has this fix? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Whilst the client now supports responding to ping messages from the server with a pong, there's no mechanism for WebSocketGraphQlClient to send a regular ping to the server itself. As per the graphql-ws spec these are bi-directional messages so should be supported either way around.
The apollo graphql client supports similar functionality via the "keepalive" option from the graphql-ws ClientOptions - perhaps a similar approach would work well here as well?
The text was updated successfully, but these errors were encountered: