- From: Philippe Le Hegaret <plh@w3.org>
- Date: Tue, 10 Dec 2013 17:54:05 -0500
- To: Ilya Grigorik <igrigorik@google.com>
- Cc: Jatinder Mann <jmann@microsoft.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
On Wed, 2013-12-04 at 15:04 -0800, Ilya Grigorik wrote: > There have been multiple requests in the past to expose the "bytes > transferred" as part of Nav/Resource Timing API. While this is not a > panacea, I do think it would be valuable and could address a lot of > use cases we're discussing here... Or, to be more precise, give the > developers the basic primitive to then build up their own abstractions > to drive BW-estimation and similar use cases. Btw, this came up again on the table during our f2f on Resource Timing L2 [1]. I added a note about it in our dashboard after that [2]. So, while we're not good at having a clear list of features we're considering for .next, this one is definitively in it. Now, I don't believe we considered it for Nav Timing yet. Philippe [1] http://www.w3.org/2013/11/14-webperf-minutes.html#item08 [2] http://www.w3.org/wiki/Web_Performance/Publications
Received on Tuesday, 10 December 2013 22:54:08 UTC