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

Re: [Navigation Timing] Adding radioAwake attribute

From: Andy Davies <dajdavies@gmail.com>
Date: Wed, 4 Jul 2012 18:59:54 +0100
Message-ID: <CABbusA+xZc+dY3OmfDhcOVbUVQ7mt87ZRCOjeuE18C3-_hgvWw@mail.gmail.com>
To: Ilya Grigorik <igrigorik@google.com>
Cc: public-web-perf@w3.org
On 29 June 2012 21:20, Ilya Grigorik <igrigorik@google.com> wrote:
> +1. It's always a gamble on mobile today to figure out if you're going to
> incur the extra cost of waiting for radio, or not.. which adds a significant
> amount of latency to the connection. Not sure if it's also useful to
> explicitly distinguish "low power" vs "sleep" modes, but at the very least,
> "radioAcquire{start, end}" events are much needed additions to both specs.
> ig
> P.S. radioAcquire* is likely not the right name.

Does it need a new start attribute - won't it be the same as
fetchStart in navigation timing?

Received on Wednesday, 4 July 2012 18:00:22 UTC

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