[webrtc-encoded-transform] Clarify why the writable stream backpressure should be disabled (#188)

saschanaz has just created a new issue for https://github.com/w3c/webrtc-encoded-transform:

== Clarify why the writable stream backpressure should be disabled ==
https://w3c.github.io/webrtc-encoded-transform/#stream-creation

>[Set up](https://streams.spec.whatwg.org/#writablestream-set-up) [this](https://webidl.spec.whatwg.org/#this).[[writable]] with its [writeAlgorithm](https://streams.spec.whatwg.org/#writablestream-set-up-writealgorithm) set to [writeEncodedData](https://w3c.github.io/webrtc-encoded-transform/#abstract-opdef-writeencodeddata) given this as parameter and its [sizeAlgorithm](https://streams.spec.whatwg.org/#writablestream-set-up-sizealgorithm) to an algorithm that returns 0.
>
>Chunk size is set to 0 to explictly disable streams backpressure on the write side.

https://github.com/w3c/webrtc-encoded-transform/pull/108 disabled it and added some notes, but the intention is not clear why it should be disabled. The note only says it's disables by letting sizeAlgorithm to return 0 (which I think it should set highWaterMark to Infinity instead).

Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/188 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 22 June 2023 14:48:31 UTC