- From: Adam Rice <notifications@github.com>
- Date: Sun, 16 May 2021 18:54:45 -0700
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 17 May 2021 01:55:01 UTC
> @ricea that's was the motivation for raising this issue. On client side it should be possible to detect if transmission is ongoing or idle. I think you misunderstood my point, which is that it is not possible at all. No API change can make it possible. The information is simply not available to the client. > An event announcing the start of chunk transmission will reduce the problem back again to the simple formula transferred_bits/transmission_duration. Interestingly, in Node.js this event already exists since a while, it is called readable [2] which offers this missing piece This Node.js code doesn't measure anything meaningful, and certainly not the speed of the network. It's basically just a benchmark of how fast Node can emit the "data" event. -- 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/1126#issuecomment-841924825
Received on Monday, 17 May 2021 01:55:01 UTC