-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Relay and GraphQL QueryStreams #652
Comments
Subscriptions are designed as a sort of declarative analogue to imperative stream mechanisms (querying data inside a stream callback could cause the n+1 query problem because the streams aren't statically conposable). What specific functionality about streams would you want separate from the subscriptions API? (see the issue for this). |
Just checking. This is exactly the use-case that GraphQL Subscriptions are meant to address. This is still an active area of exploration, and we're tracking progress at #541. |
Thanks I'll follow the issue.. PS did some digging found this https://gist.github.com/ngthorg/21a986962228f53a3ec5 .. your thoughts? |
We've documented our thoughts on subscriptions pretty extensively in a dedicated blog post :-) |
Is there a Relay construct analogous to Mongoose QueryStreams (http://mongoosejs.com/docs/2.7.x/docs/querystream.html) with Relay? i.e. rather than polling the GraphQL endpoint, perhaps subscribe to a QueryStream over web-sockets into the GraphQL server?
The text was updated successfully, but these errors were encountered: