- From: Arvind Jain <arvind@google.com>
- Date: Sat, 17 May 2014 16:15:34 -0700
- To: Kornel Lesiński <kornel@geekhood.net>, Jonas Sicking <jonas@sicking.cc>
- Cc: public-web-perf <public-web-perf@w3.org>
Received on Saturday, 17 May 2014 23:16:03 UTC
I've added a Beacon-Age header to the beacon request per comments on this thread. https://w3c.github.io/web-performance/specs/Beacon/Overview.html Please review and let me know if this looks good. On Fri, May 16, 2014 at 3:48 PM, Kornel Lesiński <kornel@geekhood.net>wrote: > On 15.05.2014, at 13:52, Arvind Jain <arvind@google.com> wrote: > > > Jonas, your alternate suggestion seems easy too. I'd prefer to keep the > Beacon spec as minimal as possible. Kornel, would Jonas' suggestion address > your concern? > > I'd have to ensure that I calculate the time offset only uncached page > load (or make an extra XHR request to get time) and hope the offset doesn't > change too often. That's an extra complication for cached/offline/phonegap > apps. It's doable in most cases, but it's not ideal. > > > I wonder whether we could extend Age response header to be used as a > request header: > http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.6 > > -- > regards, Kornel > > >
Received on Saturday, 17 May 2014 23:16:03 UTC