Re: [streams] Change the model for ReadableStream to have async read() (#288)

>> We are about to introduce a pool mechanism (or pending read ops, if you prefer async read) into ReadableByteStream. We should replicate the mechanism into ExclusiveReader and it will get more and more complex.

> I don't think it's quite that bad. The design of ExclusiveReader is largely meant to just wrap the logic already present in Readable(Byte)Stream. There shouldn't be any duplication, at least in theory.

It depends on the design: If we choose (2) in https://github.com/whatwg/streams/pull/288#issuecomment-75780840, you are right. Otherwise, we should have two separate pools for the stream and the active reader and they sometimes interact with each other.


---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/pull/288#issuecomment-76346673