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

Re: [HighResTime] Web Worker support

From: James Simonsen <simonjam@chromium.org>
Date: Tue, 14 May 2013 11:20:11 -0700
Message-ID: <CAPVJQinQ42VBo_5Afot7Qg7vee9gQ-WyeDPSGKUW3RvGuki_Yw@mail.gmail.com>
To: public-web-perf <public-web-perf@w3.org>
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)?

Received on Tuesday, 14 May 2013 18:20:39 UTC

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