Skip to content
This repository has been archived by the owner on May 16, 2019. It is now read-only.

Subscription support #27

Open
tw opened this issue Oct 4, 2018 · 2 comments
Open

Subscription support #27

tw opened this issue Oct 4, 2018 · 2 comments

Comments

@tw
Copy link

tw commented Oct 4, 2018

In the wiki you mention that it's not supported yet.

Is it desired/anyone working on it? It's something I'd like - and might be able to start work on at some point.

@pgutkowski
Copy link
Owner

Hi @tw,

I don't really know what is demand for subscriptions, but I guess it would be really nice addition to KGraphQL. I'm almost sure nobody is working on it, so feel free to start!

Do you already have any ideas/intial design? I would love to hear them.

@tw
Copy link
Author

tw commented Oct 8, 2018

@pgutkowski thanks for the response. I myself would like them so I could start to consider using it at work (we're currently using graphql-java, I'd like something a bit smaller, and more native).

I suppose I'd probably use a combination of coroutines/channels to handle subscriptions - especially now co-routines are non-experimental.

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

No branches or pull requests

2 participants