- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Aug 2018 09:47:03 +0000
- To: public-webrtc-logs@w3.org
Yes, what Randell said is still true but I don't think it matters. I made a suggestion in the Chromium issue how this can be fixed by browser vendors. For details, see [my comment in the issue](https://bugs.chromium.org/p/chromium/issues/detail?id=878682#c24). I don't see anything in the example you've provided that would work around the current bug. This is how it's actually supposed to work. Send until `bufferedAmount >= myHighWaterMark`. Pause. Continue sending once the event has been fired. Awkward but working as intended. Btw, funny enough the datatransfer example is likely to suffer from bad throughput once this is fixed by Chrome and Firefox since SCTP will not have enough buffered data. I would suggest using a higher high water mark to ensure a couple of chunks are in the buffer. -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1979#issuecomment-417613095 using your GitHub account
Received on Friday, 31 August 2018 09:47:04 UTC