Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877)

> I don't think the stream's buffering should depend on the type of its current reader. If a user really wants all reads from a byte stream to be as efficient as possible, then they can just set the stream's high water mark to 0. That way, the stream will only pull when there are pending read requests.

I'm concerned that this may leave the creators of readable byte streams in the uncomfortable position of having to choose between optimal behaviour for byob readers or optimal behaviour for default readers. However, I agree that depending on the type of the current reader is too problematic.

Do you think you can get "always pull() as long as the queue has space and progress is happening" semantics working? Even if it's not working, it would be helpful to see a work-in-progress that I could work from.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/877#issuecomment-365865223