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

Subscriptions #86

Closed
ronag opened this issue Aug 23, 2015 · 4 comments
Closed

Subscriptions #86

ronag opened this issue Aug 23, 2015 · 4 comments

Comments

@ronag
Copy link

ronag commented Aug 23, 2015

We need a way to listen to changes performed by someone else than the local client in order to build true real-time apps based on GraphQL. Similar to how Firebase and Meteor work.

I know this is being discussed on Slack but a proper ticket is missing.

@OlegIlyenko
Copy link
Contributor

I made a small write-up about my thought on a GraphQL subscription mechanism:

https://gist.github.com/OlegIlyenko/a5a9ab1b000ba0b5b1ad

Any comments and thoughts on this idea are appreciated :)

@zuhair-naqvi
Copy link

+1

@leebyron
Copy link
Collaborator

leebyron commented Jan 9, 2016

Just wanted to add that a blog post was written on this topic as well: http://graphql.org/blog/subscriptions-in-graphql-and-relay/

Subscriptions is one piece of a larger topic of live data and asynchronicity that we plan on covering in the future with GraphQL. There are already experiments underway to better understand what the right decisions will be.

@leebyron
Copy link
Collaborator

leebyron commented May 1, 2018

Closing this aging issue since Subscriptions are captured in spec

@leebyron leebyron closed this as completed May 1, 2018
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

No branches or pull requests

4 participants