Re: [streams] Generalized and precise flow/buffer control (#301)

Some logs of the last week's discussion
- For the initial release, `read` method is the only way for the consumer to tell the stream how fast the consumer is / how much the consumer is fine with getting buffered. Readable stream doesn't expose setHWM to the consumer.
    - [tyoshino] Re: naming, I prefer pullAmount (or something similar) to HWM as HWM sounds like assuming that there's a queue.
    - [tyoshino] If we add a similar method to the writable side, it should use "space" not "queueSize" for its name. We have many queues behind a writable stream (JS, C++, kernel, device, ...). If we say "queue", we need to tell what the "queue" means and forces the consumer to think of the details behind the writable stream.


---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/301#issuecomment-84875887