Re: [whatwg/streams] Idiomatic Way to Explicitly Tell an Underlying Transform Stream to Flush to the Sink (#960)

Thanks. I was vaguely hoping we could do this as part of the piping process. E.g. using `pipeThrough(zlib, { signal })` where `signal` is a subclass of `AbortSignal` (call it `PipeSignal`) whose corresponding `PipeController` has a method like `requestFlush()`. But, that would put the responsibility in the hands of the author of the service worker code, whereas you've clarified that it would be better propagating automatically from the readable stream.

In that case @ricea's sketch seems like the obvious design. I wonder if generalizing it so that you could propagate more messages (of which `"flush"` or `"sync"` was just one) would make it solve enough use cases to be worth the extra complexity.

-- 
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/960#issuecomment-436787540