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

Feature Request: GraphQL over SSE #6

Open
d-exclaimation opened this issue Sep 22, 2021 · 1 comment
Open

Feature Request: GraphQL over SSE #6

d-exclaimation opened this issue Sep 22, 2021 · 1 comment
Assignees
Labels
feature request A potential new feature implementation potential Potential issue(s) or enchancement but unconfirmed

Comments

@d-exclaimation
Copy link
Owner

Description

Implement GraphQL Subscription over SSE (Subscription operation only). Shouldn't be too difficult as to GraphQL over WebSocket. However, I need to support the graphql-sse protocol to be fully client compatible. Not sure whether to support other protocols and client implementation.

Prerequisites

Implementation and Plans

  • Start with focusing solely on Distinct connections mode on HTTP/2 (require enabling HTTP/2 for akka-http).
  • Continue with implementing Single connection mode which require a lot more configuration with the HTTP side of the applications but allow for HTTP/1.1.
@d-exclaimation d-exclaimation added enhancement New feature or request potential Potential issue(s) or enchancement but unconfirmed labels Sep 22, 2021
@d-exclaimation d-exclaimation self-assigned this Sep 22, 2021
@d-exclaimation d-exclaimation added feature request A potential new feature implementation and removed enhancement New feature or request labels Sep 22, 2021
@d-exclaimation
Copy link
Owner Author

d-exclaimation commented Sep 22, 2021

Unit Test Addition

Server-Side Events

  1. Able parse query from request.
  2. Using a simple schema, able to execute GraphQL Subscription operation using the graphql-sse protocol.
    a. Able to format response as text encoded in next message event.
    b. Able to format response as text encoded in complete message event.
  3. Able to handle closing and opening connection.
  4. HTTP/2 support for Distinct connection mode.
  5. HTTP/1 support for Single connection mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request A potential new feature implementation potential Potential issue(s) or enchancement but unconfirmed
Projects
None yet
Development

No branches or pull requests

1 participant