Ian Ker-Seymer

This is awesome.

It's not *that* big of a deal, but the 304 still means a server round trip, when it could be avoided :)

The main issues we would have with Agoo's imementation are: 1. It does not support GraphQL Ruby, I think this is vital. Because of this, GraphQL support at the http...

1. For subscriptions, there is an adapter API needed to support GraphQL Ruby 2. It has a lot of funtionality out of the box that would otherwise be a lot...

Also, I'm interested in the relationship of Agoo Iodine. Do they work together in certain ways?

so that adapter interface is the low-level interface which Iodine would implement, the actual user-facing portion is documented here: https://graphql-ruby.org/guides#subscriptions-guides

ActionCable is one *possible* adapter, if you use Rails. Not everyone uses Rails (we don’t 😀). Also, wouldn’t the performance of the Action able adapter be worse than using the...

> look-ahead: I understand the concept of look ahead. What I didn't get was why it was needed if the Ruby code can see the query. Wouldn't it have all...

> I might be quiet, but it's because I'm listening and learning. > > Let me see if I understood correctly: > > * Would GraphQL API calls use HTTP...

@rmosolgo thank you! https://github.com/Envek/graphql-anycable/blob/master/lib/graphql/subscriptions/anycable_subscriptions.rb demonstrates the interface I was proposing to use perfectly 😀