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

Re: Unified Timing: Navigation, Resource and User Timing Updates

From: Christian Biesinger <cbiesinger@gmail.com>
Date: Tue, 26 Jul 2011 17:52:22 -0700
Message-ID: <CACpOFMtLKKrJsPJbEMa0cFMhAs1cB764ja+G5nUY8YFB7dEzhQ@mail.gmail.com>
To: Jatinder Mann <jmann@microsoft.com>
Cc: Olli Pettay <opettay@mozilla.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
Just to close this thread, the changes have been undone and the
performance timeline part moved to a separate spec.
http://lists.w3.org/Archives/Public/public-web-perf/2011Jul/0091.html

-christian

On Tue, Jul 5, 2011 at 12:17 PM, Jatinder Mann <jmann@microsoft.com> wrote:
> Christian,
>
> We have spent the last few conference calls discussing just this matter. The changes made to the Navigation Timing spec do not impact the existing implementations of Navigation Timing; these are additive changes that will ensure Navigation Timing and future metrics (Resource Timing, User Timing and any future timings metrics) will have a consistent way to retrieve data. The main changes made to the spec were to include definitions of the PerformanceEntry and PerformanceEntryList interfaces.
>
> In the 6/22 conference call, http://lists.w3.org/Archives/Public/public-web-perf/2011Jun/0090.html,  the working group had agreed that updating Navigation Timing to include PerformanceEntry and PerformanceEntryList interfaces will not take it out of its current state (Candidate Recommendation), but will call for a one month period of Last Call to gather feedback on the updated delta. The bar for changes to the existing portions of the spec will be higher, as we want to focus attention on the newly added delta.
>
> In principle, the working group was happy with these forward thinking changes. Please take a moment to review the actual text changes I had submitted and provide feedback on the mailing list. Once we are sufficiently happy with the text changes made to the spec, we can take the spec to Last Call.
>
> Thanks,
> Jatinder
>
> -----Original Message-----
> From: Christian Biesinger [mailto:cbiesinger@gmail.com]
> Sent: Monday, July 04, 2011 6:01 AM
> To: Jatinder Mann; Olli Pettay
> Cc: public-web-perf@w3.org
> Subject: Re: Unified Timing: Navigation, Resource and User Timing Updates
>
> Unfortunately I missed the call where this was discussed. I see that these are fairly major changes in a spec that is already in CR. Should we really make such big changes at this late point? I was hoping that at CR, the spec would be stable enough that it can be implemented without changing under the foot.
>
> -christian
>
> On Sat, Jul 2, 2011 at 1:48 AM, Jatinder Mann <jmann@microsoft.com> wrote:
>> As per our discussion to unify all Web Performance Timing
>> specifications with an inheritance model and consistent API for data
>> retrieval, we have made updates to Navigation, Resource and User
>> Timing specification. Please review these changes and provide feedback.
>>
>>
>>
>> Navigation Timing:
>> http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Over
>> view.html
>>
>>
>>
>> Resource Timing:
>> http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/ResourceTiming/Overvi
>> ew.html
>>
>>
>>
>> User Timing:
>> http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/UserTiming/Overview.h
>> tml
>>
>>
>>
>> Have a great long weekend!
>>
>>
>>
>> Thanks,
>>
>> Jatinder
>>
>>
>>
>>
>
>
Received on Wednesday, 27 July 2011 00:52:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 July 2011 00:52:51 GMT