Thanks for the link. From what I can read it seems that there needs to be some concept of pausing or stopping and resuming a stream. This is one of the outstan

Thanks for the link. From what I can read it seems that there needs to be some concept of pausing or stopping and resuming a stream. This is one of the outstanding issues with promises too. That there is no standard way to cancel them. I hope TC39 are considering this as part of the spec. It's less of an issue in the client, because you are less likely to encounter big firehoses of data. But I have had the issue with webrtc data processing, and some flow control / back pressure mechanisms would be awesome. We were able to just use node streams, but would be nice if there was an elegant solution for async iterators too. Node streams are good, but also add a lot of complexity. And debugging back-pressure issues can be very tricky in my experience, as they can manifest themselves in a variety of different ways.