Is there a general strategy for streaming intermittent data that's compatible with use of interceptors? I'm looking for the best way to handle GraphQL subscriptions, where we want to periodically put a blob of JSON into the response (probably driven by a core.async channel). But at the point where this executes, there's a couple of other interceptors on the stack that should be involved. Looking at http://pedestal.io/reference/streaming my best bet may be to return a callback function and stream the content, but them I'm duplicating a bunch of logic that (in the normal, non-subscription case) is inside a couple of interceptors .. .things like choosing a status code, and converting from Clojure data to JSON. Thoughts?

The SSE code would be good, but is not compatible with GraphQL clients, which simply expect the stream of JSON blobs.

And I also would like to know when the client closes the connection, so that we can do some cleanup.

Digging deeper ... looks like web sockets are a valid approach for GraphQL subscriptions.