-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Closed as not planned
Labels
Stalearea/graphqlIssues related to GraphQL support on Dgraph.Issues related to GraphQL support on Dgraph.area/operationsRelated to operational aspects of the DB, including signals, flags, env vars, etc.Related to operational aspects of the DB, including signals, flags, env vars, etc.communityIssue or PR created by the community.Issue or PR created by the community.kind/bugSomething is broken.Something is broken.status/acceptedWe accept to investigate/work on it.We accept to investigate/work on it.
Description
DGraph currently uses a depreciated and insecure websockets protocol: subscriptions-transport-ws. They recommend changing to use graphql-ws.
https://github.com/enisdenjo/graphql-ws/blob/master/PROTOCOL.md
The creator of the graphql-ws even suggested that you use it in DGraph Discuss. This would have to be updated before V1 is released, as it is NOT compatible with the other protocol.
Hasura uses both, so you could easily add the new protocol without causing depreciation problems!
J
leonhma
Metadata
Metadata
Assignees
Labels
Stalearea/graphqlIssues related to GraphQL support on Dgraph.Issues related to GraphQL support on Dgraph.area/operationsRelated to operational aspects of the DB, including signals, flags, env vars, etc.Related to operational aspects of the DB, including signals, flags, env vars, etc.communityIssue or PR created by the community.Issue or PR created by the community.kind/bugSomething is broken.Something is broken.status/acceptedWe accept to investigate/work on it.We accept to investigate/work on it.