Re: [whatwg/fetch] Expose Stream Watermarks (#689)

@benjamingr The lack of backpressure is a deficiency in Chrome's implementation. See https://bugs.chromium.org/p/chromium/issues/detail?id=535793.

In general, if you need to _add_ buffering, piping through a `new TransformStream(undefined, new ByteLengthQueuingStrategy({highWaterMark: 16 * 1024 * 1024}))` is the way to go.

_Removing_ buffering would be somewhere between "hard to implement" and "infeasible". There are multiple layers of buffering in place, all of which serve a purpose and some of which are outside of the control of the browser implementer. It might be possible to have a "hint" to implementations that a particular fetch wants reduced buffering, but I expect it would end up with all implementations ignoring the hint completely.

-- 
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/fetch/issues/689#issuecomment-378165013