- From: Steven Robertson <strobe@google.com>
- Date: Mon, 18 Jun 2012 13:42:50 -0700
- To: Mark Watson <watsonm@netflix.com>
- Cc: Aaron Colwell <acolwell@google.com>, "Sunyang (Eric)" <eric.sun@huawei.com>, "public-html-media@w3.org" <public-html-media@w3.org>
On Mon, Jun 18, 2012 at 12:41 PM, Mark Watson <watsonm@netflix.com> wrote: > If we are going to provided download progress information for adaptive > streaming though this API, then ideally it should have the following > properties: > - progress information should be associated with the URL/byte range > - the HTTP response time should be available and separated from any time > spend doing redirections, CORS pre-flights etc. > - the bytes received information should be provided in the form of triples > (reception start, reception end, bytes received) so that the script does not > average over time periods where the client was (deliberately) not receiving > data (or, equivalently, we could have reception start/stop/progress events > that come with timestamps). +1. Will implementations have the option of initiating multiple requests per source in parallel (to reduce startup latency)? Steve
Received on Monday, 18 June 2012 20:43:59 UTC