Skip to content
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

Implement graphql-transport-ws protocol for websocket subscriptions (webmvc & webflux) #1200

Merged
merged 1 commit into from Aug 29, 2022

Conversation

srinivasankavitha
Copy link
Contributor

@srinivasankavitha srinivasankavitha commented Aug 23, 2022

Pull Request type

  • Bugfix
  • Feature
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Other (please describe):

Changes in this PR

This PR adds support for the newer graphql-transport-ws protocol for websocket subscriptions.

  1. Refactored and fixes bugs with webmvc implementation of graphql-transport-ws implemented in feat: implement GraphQL over WebSocket Protocol #686
  2. Remove graphql-dgs-subscriptions-transport module and corresponding autoconfigure introduced as part of feat: implement GraphQL over WebSocket Protocol #686
  3. Implement webflux implementation of graphql-transport-ws with tests

The implementation is additive and preserves backwards compatibility with the deprecated graphql-ws implementation. The control flow is based on the presence of protocol headers. Eventually, we will remove support for the deprecated protocol, but for the time being, DGSs can support both clients.

@DefaultValue("/subscriptions") var path: String = "/subscriptions"
@DefaultValue("/subscriptions") var path: String = "/subscriptions",
/** Connection Initialization timeout in ms. */
@DefaultValue("10000") var connectionInitTimeout: String = "10000"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not make this a Duration, Spring will handle changing the seconds (s), millis (ms), etc to the proper value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants