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

Re: [HighResTime] Web Worker support

From: James Simonsen <simonjam@chromium.org>
Date: Wed, 4 Sep 2013 13:35:22 -0700
Message-ID: <CAPVJQimk8=5UjVQZM2ejyzJCTA0HJXMXONUGuUAw9kzb8w1icg@mail.gmail.com>
To: public-web-perf <public-web-perf@w3.org>
On Tue, May 14, 2013 at 11:20 AM, James Simonsen <simonjam@chromium.org>wrote:

> Sorry for being late getting back to this thread...
>
> On Thu, Apr 18, 2013 at 10:44 AM, Jatinder Mann <jmann@microsoft.com>wrote:
>
>>  Ben,****
>>
>> ** **
>>
>> If you’re just looking at deltas, differences between two time values,
>> the origin shouldn’t matter. Is there a case where deltas wouldn’t be good
>> enough and you would want the absolute numbers?****
>>
>> ** **
>>
>> If we were are to provide the origin time as a separate value (e.g.,
>> performance.originTime), it would need to be in the same sub-millisecond
>> resolution in order to be comparable with other DOMHighResTimeStamps; the
>> spec currently suggests one thousandth of a millisecond. Double precision
>> may be able to support that for milliseconds since Unix epoch.
>>
>
> I don't fully understand the originTime. Is this effectively a global
> monotonic clock across all processes (workers and tabs)?
>

Ping? Are we going to do anything about this?

James
Received on Wednesday, 4 September 2013 20:35:53 UTC

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