Re: [whatwg/streams] Stream Reader: event to detect first byte added to internal buffer (#1126)

The streams API for non-byte-streams treats chunks as atomic units, so there's no concept of a "first byte".

Eventually I expect fetch will use byte streams instead, but even then, the "time for first byte" will just be the same as "time for first chunk".

I don't know about other browsers, but Chrome we handle network input in chunks anyway, so there really isn't a concept of "first byte" distinct from "first chunk" (despite [what the resource timing API may imply](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming/responseStart)).

What this means for measuring throughput is that `chunkEndTime` will always be the same as `chunkStartTime`, so exposing them separately would not help you.

-- 
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-838982859