RE: More on workerStart from Todd Reifsteck on 2015-06-12 (public-web-perf@w3.org from June 2015)

From: Todd Reifsteck <toddreif@microsoft.com>
Date: Fri, 12 Jun 2015 03:56:58 +0000
To: Ilya Grigorik <igrigorik@google.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: <CY1PR0301MB0619D5770A2137FF8CDB26A9C2BB0@CY1PR0301MB0619.namprd03.prod.outlook.>

Agreed

From: Ilya Grigorik [mailto:igrigorik@google.com]
Sent: Wednesday, June 10, 2015 12:05 PM
To: Todd Reifsteck
Cc: Boris Zbarsky; Justin Rogers; Jonas Sicking; public-web-perf@w3.org; Przemysław Pietrzkiewicz; Travis Leithead
Subject: Re: More on workerStart

On Tue, Jun 9, 2015 at 10:38 PM, Todd Reifsteck <toddreif@microsoft.com<mailto: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 Friday, 12 June 2015 03:57:29 UTC