Re: [whatwg/streams] Provide a way for the underlying sink to signal write progress? (#876)

Certainly, silly window syndrome is an anti-pattern. But the jumps from full to empty and back again are an anti-pattern as well (the congestion window can reset and *slow start* is initiated). The word *desired* from `desiredSize` implies to me that this is the recommended chunk size the controller wants to see and that implies that the chunk shouldn't be too large and shouldn't be too small. I'm not sure it's a good idea to leave this task up to the application or other controllers (e.g. by doing `Math.min(writer.desiredSize, preferredChunkSize, remainingBytes)`.

As an idea: We could add a more fine granular progress feedback as mentioned by @domenic and couple it with requiring to provide a `lowWaterMark`. So, `.ready` would not resolve before `.desiredSize >= .lowWaterMark`.

-- 
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/876#issuecomment-365293982