Re: [Beacon] Required Beacon-Age: handling. from Arvind Jain on 2014-08-18 (public-web-perf@w3.org from August 2014)

From: Arvind Jain <arvind@google.com>
Date: Sun, 17 Aug 2014 23:14:07 -0700
To: Sigbjorn Finne <sof@opera.com>
Cc: public-web-perf <public-web-perf@w3.org>, Adam Barth <abarth@chromium.org>, David Benjamin <davidben@chromium.org>
Message-ID: <CAOYaDdPsG_nLppoWi7SbpbBawO_8Jbtm2bfCRwyVF=ZE0oCsNQ@mail.gmail.com>

#11 is left to the user agent. In the usual case, it is hopefully soon
after step 10, but it can de delayed. Is it what you are asking?

On Sun, Aug 17, 2014 at 10:12 PM, Sigbjorn Finne <sof@opera.com> wrote:
> Den 18.08.2014 04:03, skreiv Arvind Jain:
>
>> requestTime should be set to the time immediately after sendBeacon()
>> is called. So it should be before the actual Fetch is performed. The
>> actual Fetch may be performed quite a bit later (e.g. if the user
>> agent decides to delay the transmission).
>>
>
> That makes sense, what about the other end of the interval that the age
> value captures, when is it assumed sampled, i.e., when is step 11 performed?
> (That was what I was referring to, sorry about confusing the spec naming.)
>
> --sigbjorn

Received on Monday, 18 August 2014 06:14:35 UTC