- From: Ilya Grigorik <notifications@github.com>
- Date: Fri, 19 Jun 2015 08:19:41 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
Received on Friday, 19 June 2015 15:20:09 UTC
Slight, but relevant tangent: understanding impact of redirects, preflights, etc, is important for performance telemetry -- see https://github.com/w3c/resource-timing/issues/21. The lack of access and visibility into these stages is a common complaint against current Nav+ResourceTiming APIs. It'd be nice if we could rationalize all this stuff between the various use cases. --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/66#issuecomment-113546545
Received on Friday, 19 June 2015 15:20:09 UTC