Ilya Grigorik

> I assume we can't use existing timing attributes to implicitly expose whether a page is fetched? If not, then I wonder if another option could be to introduce a...

We need security folks to chime in on this one. I believe one potential side effect here is that this information would expose users behind HTTP proxies: the UA would...

Yes, the edge node would need to emit the Server-Timing header. Practically speaking, if we're talking CDN use cases, you're talking about caching in addition to early termination, and as...

> Can there be some way to exactly link these via API? For example: > > WorkerPerformance.getEntriesByClientId(clientId) call to filter by client ids > Adding a clientId field into the...

Ben, can you enumerate more specifically exactly what kind of data you're looking for and the motivation for exposing it? I.e. enumerate the use cases.. I agree with Yoav that...

> At a most basic level I'd like to get timing information from the local cache. For example, if a request was a cache miss how long did it take...

> Fundamentally though, one still has to check a cache before the request goes out. This check has to happen before requestStart (because you must determine if you are making...

> If an image is requested first by and later on by a CSS url(), which initiator type should it have? Personally, I'd expect it to report "img" for the...

But the reused resource must come from somewhere, right.. a shared cache? In this instances it's probably the memory cache, but it also doesn't have to be - e.g. evicted...

> It is coming from the memory cache, but I don't think we want to expose each call to the memory cache in resource timing... I'm not saying we should...