- From: Ilya Grigorik <igrigorik@google.com>
- Date: Mon, 4 May 2015 16:19:39 -0700
- To: John Scharber <jscharber@vidscale.com>
- Cc: public-web-perf <public-web-perf@w3.org>
Received on Monday, 4 May 2015 23:20:49 UTC
Hi John. On Wed, Apr 29, 2015 at 2:25 PM, John Scharber <jscharber@vidscale.com> wrote: > From a mobile device perspective, it would suggest a few additional > capabilities: > > 1) Limit beacon reporting to specific network types, WiFi, Fixed, etc > 2) For mobile networks, 2/3/4G, limit sending beacons to specific link > states like active vs. idle > 3) Aggregate beacons for the same destination > Yup, all great suggestions. If you're interested, check the archives.. we discussed all of the above while iterating on the spec. Hence the provisions for "Beacon-Age" header, language for delaying and prioritizing delivery, and so on. AFAIK, current implementations (FF, Chrome) do take advantage of some (e.g. prioritization) but not all (e.g. delayed delivery) of these. That said, nothing stops them from adding these capabilities at any point either. ig
Received on Monday, 4 May 2015 23:20:49 UTC