W3C home > Mailing lists > Public > public-web-perf@w3.org > January 2013

Re: Adding protocol information to Resource Timing

From: Arvind Jain <arvind@google.com>
Date: Tue, 29 Jan 2013 15:32:40 -0800
Message-ID: <CAOYaDdO_wPTzkT2s63w6G+bONVvWtBKj9h8YEgfW4bZ7xvde9w@mail.gmail.com>
To: James Simonsen <simonjam@chromium.org>
Cc: "McCall, Mike" <mmccall@akamai.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>, "Jain, Shakesh" <shjain@akamai.com>
I agree with James. There's the case where RUM collection is done by a
third party but even there, this info could be collected outside of the
resource timing API.



On Tue, Jan 29, 2013 at 2:52 PM, James Simonsen <simonjam@chromium.org>wrote:

> I can't speak for everyone, but my opinion is that Resource Timing should
> not repeat information that the server already knows. You should be able to
> record the protocol on the server side.
>
> James
>
>
> On Mon, Jan 28, 2013 at 7:09 AM, McCall, Mike <mmccall@akamai.com> wrote:
>
>> 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).
>>
>> Since the Resource Timing specification already enumerates the resources
>> for a
>> given page, it seems like it would make sense to also include which
>> protocol was used to fetch a given resource.
>>
>> What does the group think?
>>
>> Thanks,
>>
>> Mike
>>
>> 1.
>> https://groups.google.com/forum/?fromgroups=#!topic/spdy-dev/ERaEDaTnt7w
>>
>>
>>
>
Received on Tuesday, 29 January 2013 23:33:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:34 UTC