-
Notifications
You must be signed in to change notification settings - Fork 42
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
GraphQL Subscriptions #8
Comments
subscriptions are not currently supported. it's something we'd like to support at some point but i wouldn't say it's on our immediate roadmap. we'd happily assist with any contribution for such a feature |
Thanks for the quick confirmation! I don't think I could help anytime soon since I haven't worked with golang yet. Also, I would believe gloo would have to support websockets too right? |
are you referring to websockets for clients of QLoo? or the ability for qloo to connect to upstreams that communicate via websockets? not currently supported either way |
Just websockets for the clients. I was just wondering if the support for websockets has to be first added to Gloo and then add subscriptions to QLoo. |
we haven't tested websockets with Gloo, but they should "just work" as long as the upstream service (in this case QLoo) supports them. QLoo however doesn't have support for websockets built in, nor subscriptions (yet). |
Would love to see this supported |
while we at solo haven't had time to work on this, I believe @deorbit has been looking into this. i'm interested as well, but probably unable to get to it in the near future |
Firstly, this project is amazing. I have been thinking of writing something like this (dynamic, config based GraphQL gateway) for use in my projects.
I tend to use GraphQL subscriptions for most of my realtime use cases and was wondering if QLoo supports it.
To be honest, I haven't gotten around to trying QLoo on my cluster yet, so I guess it could probably "just work" but since I couldn't find any mention of it in the documentation, I'm asking here.
Also, if it isn't supported as of today, is it on the roadmap for a future release?
The text was updated successfully, but these errors were encountered: