Re: More on workerStart from Ilya Grigorik on 2015-06-10 (public-web-perf@w3.org from June 2015)

From: Ilya Grigorik <igrigorik@google.com>
Date: Wed, 10 Jun 2015 12:05:23 -0700
To: Todd Reifsteck <toddreif@microsoft.com>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, Justin Rogers <justrog@microsoft.com>, Jonas Sicking <jonas@sicking.cc>, "public-web-perf@w3.org" <public-web-perf@w3.org>, Przemysław Pietrzkiewicz <ppi@google.com>, Travis Leithead <travis.leithead@microsoft.com>
Message-ID: <CADXXVKqmVXksG8-tsDcxhN=mxZHLMj2nGt5-kdPAoCftBVfVeQ@mail.gmail.com>

On Tue, Jun 9, 2015 at 10:38 PM, Todd Reifsteck <toddreif@microsoft.com>
wrote:

> We've defined the following requirements..
> * We'd like an easy way to get the workerStart within a context
> * We'd like a way to easily convert workerStart to a new timeOriginBasis
>

I think we should consider expanding above requirements to a broader use
case of "I would like to map timestamps retrieved from a worker or another
window object into my current timeline". Doing so requires that we clearly
define time origin's for each (in particular, dedicated vs shared workers),
and define an API to get the offsets.

ig

Received on Wednesday, 10 June 2015 19:06:31 UTC