Re: [whatwg/streams] TransformStream probably doesn't need two strategies (#190)

What about when the location of the bottleneck is unstable and changes?

Like if the ultimate sink is an unreliable internet connection or some other sink that's usually rapid in its consumption of chunks, but can have long periods of stalling. And the TransformStream in question has a very heavyweight, slow transform that in ideal operations, would be the bottleneck of the pipe. But when the sink suddenly stalls, that sink becomes the bottleneck instead, and queueing up the results of the slow transform is helpful, as the work is done 'ahead of time' and can be rapidly drained when downstream conditions improve again.

-- 
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/190#issuecomment-257127766