As of 2013-11-05
the goal is to show how much time resource requests were blocked on the network. So anything that doesn't go out on the wire doesn't need to be reported. We may need to beef up our definitions in the spec.
If a request for an resource is really fast, was it because the resource was retrieved quickly or that the resource doesn't exist and an error response delivered?
Is there any reason the resource's byte-size & compressed byte-size were not added to the ResourceTiming API?
After some internal discussions, a colleague recently started a thread[1] on the spdy-dev mailing list, asking about having an interface for developers to leverage to determine whether or not a web page resource was fetched via SPDY (or in the future, HTTP 2.0).
What is the meaning of "Timing-Allow-Origin HTTP response header rules are met"?
we should explicitly say these elements are excluded. It's already on our charter to support them in Resource Timing 2.
I understand why the spec states that connectEnd excludes SOCKS authentication etc., but don't quite understand why it excludes the SSL Handshake
I like Arvind's simpler model as well. By triggering the onresourcetimingbufferfull callback at N instead of N+1, it gives the developer the opportunity to either call clearResourceTimings() or grow the buffer incrementally via setResourceTimingBufferSize() , theoretically, with little chance for 'lost events'.
Maybe an example best practice could be provided so developers see they shouldn't have to setResourceTimingBufferSize(9999)?
304 responses should be including in Resource Timing list. We should make sure the implementations store 304 responses.
The Performance.onresourcetimingbufferfull attribute should be of type 'Function'. Other DOM objects seem to use the 'EventListener' type (and inherit EventTarget) for similar purposes. Is there any reason why onresourcetimingbufferfull is not an EventListener and why the Performance does not inherit EventTarget?
We decided to punt Web Worker support to a level 2 spec. We were mainly talking about resource downloaded inside the worker, like XHRs. What about the worker itself? Its script is actually fetched by the main document, so it seems like it should show up in the buffer and have a "worker" initiatorType.
The specification uses, without definition, the term "networking layer".