Consider suggesting to use Server Sent Events prior to Websockets

Hey,

I would like you to consider using server sent events by default and suggest this approach to the people, as we saw here in a lot of live-examples, that using websockets together with async interators in production could be a very explosive mixture.

https://www.smashingmagazine.com/2018/02/sse-websockets-data-flow-http2/

1. Maybe we could together develop a more common solution, which is inspired from: https://github.com/CodeCommission/subscriptions-transport-sse?

2. I am asking myself, why we are forced to use async-iterators as a technology, which seems to be not really ready for production purposes? Is there any alternative?

Cheers!

Start by reviewing the linked SSE/WebSockets article and the CodeCommission/subscriptions-transport-sse repository, then inspect how this project uses GraphQL subscriptions and async iterators. Done would require a decided, concrete scope for recommending or supporting SSE rather than an open-ended discussion of alternatives.

Written by the indexing model from the issue text.