RE: add "networkDuration" to Resource Timing

Thanks, Ilya. The web interface is a bit tricky to navigate and I missed that response.

To summarize and ensure I’m understanding the argument:
If 3rd parties implemented http://www.w3.org/TR/resource-timing/#timing-allow-origin, networkDuration is not necessary because sufficient information would already be included.

Is that accurate?

From: Ilya Grigorik [mailto:igrigorik@google.com]
Sent: Friday, February 27, 2015 10:31 AM
To: Todd Reifsteck
Cc: public-web-perf@w3.org
Subject: Re: add "networkDuration" to Resource Timing

From previous thread [1]: "As we discussed earlier in this thread, "networkDuration" is misleading if we include cache time, and if we don't then we're up against TAO restrictions. The whole "add new attribute discussion" is a distraction: there are many different metrics you should be measuring (and "duration" is one of them) and UAs don't need to precompute all of these.. we simply need to provide the raw data, which the current API already does."

I still believe all of the above holds and we shouldn't add networkDuration as a new attribute. That said, happy to be convinced otherwise... :)

[1] https://lists.w3.org/Archives/Public/public-web-perf/2015Jan/0031.html



On Thu, Feb 26, 2015 at 8:45 PM, Todd Reifsteck <toddreif@microsoft.com<mailto:toddreif@microsoft.com>> wrote:
I recently read through this suggestion from Steve Souders while browsing his blog and read the backlog from this mailing list on the idea.

I didn’t see an issue on ResourceTiming and NavigationTiming tracking this suggestion so I’ve added https://github.com/w3c/resource-timing/issues/13 to track it.

Thanks,
Todd