W3C home > Mailing lists > Public > public-web-perf@w3.org > August 2011

Re: [Resource Timing] Spec feedback

From: James Simonsen <simonjam@chromium.org>
Date: Mon, 22 Aug 2011 18:07:51 -0700
Message-ID: <CAPVJQikZgsdhKO9Q7SWQ0WyQHCs2yA7c3AHCHm_w+ZhViStnvg@mail.gmail.com>
To: public-web-perf <public-web-perf@w3.org>
On Thu, Aug 18, 2011 at 12:52 PM, James Simonsen <simonjam@chromium.org>wrote:

> I've been looking at implementing this again and made notes of some things
> we might want to change in the spec. Let me know what you think.
> "The startTime attribute must return..."
>    - Why doesn't this just return fetchStart? I'd like the range
>    [startTime, startTime + duration] to encompass all of the values in the
>    struct (except for the zeroed out ones). As it is now, fetchStart may occur
>    before startTime.
> After reading the processing model more carefully, I think the actual
problem is that there's a disconnect between the description and the
processing model.

Based on fetchStart's description, which links to the HTML5 spec, we should
include redirects in fetchStart. But, in the processing model, it says we
should reset fetchStart after a redirect. One of those should be fixed. I
think the processing model is correct. That matches the diagram too.

We still need to update the processing model though. It says, "Otherwise,
immediately before a user agent starts the fetching process, record the
current time as fetchStart." Since the fetching process includes redirects,
this only ever happens once per resource.

We might want to include startTime on the diagram too. It'd help make it
clear what the distinction is between fetchStart and startTime.

Received on Tuesday, 23 August 2011 01:08:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:01:09 UTC