Re: [whatwg/streams] Piping to writable streams with HWM 0? (#1158)

> that isn't already given by using ... HWM = 1

I think the OP does a good job of explaining the problem with HWM =1: it sprinkles chunks into the pipe early, just because HWM = 1 says to do it. I see no inherent reason a TransformStream requires this to operate, when it could `requestData()` on demand (when it gets a `pull()` on its readable). It doesn't require a chunk to have already been queued up, in order to work.

For sources with time-sensitive chunks — which is any source that may drop chunks as a solution to back-pressure (a camera or WebTransport datagram receiver) — operating on already-queued chunks means operating on old chunks. [Example](https://jsfiddle.net/jib1/98Lktnxy/).

-- 
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/1158#issuecomment-919241355