W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2011

[whatwg] Limiting the amount of downloaded but not watched video

From: Glenn Maynard <glenn@zewt.org>
Date: Tue, 18 Jan 2011 06:34:41 -0500
Message-ID: <AANLkTi=ph3fXtPp6AKTZ+m08iLnK2LDBgtAJfTaOviz5@mail.gmail.com>
On Mon, Jan 17, 2011 at 5:01 PM, Zachary Ozer <zach at longtailvideo.com>wrote:

> > I assume you're comparing to the bandwidth usage of flash? Does flash
> allow
> > developers to control how the media is downloaded on the client? What
> > mechanisms does it provide? Maybe we can do something similar?
>
> There are a bunch:
>
> * backBufferLength : Number - [read-only] The number of seconds of
> previously displayed data that currently cached for rewinding and
> playback.
>
> * backBufferTime : Number - Specifies how much previously displayed
> data Flash Player tries to cache for rewinding and playback, in
> seconds.
>
> * bufferLength : Number - [read-only] The number of seconds of data
> currently in the buffer.
>
> * bufferTime : Number - Specifies how long to buffer messages before
> starting to display the stream.
>
> * bufferTimeMax : Number - Specifies a maximum buffer length for live
> streaming content, in seconds.
>
> * bytesLoaded : uint - [read-only] The number of bytes of data that
> have been loaded into the application.
>
> * bytesTotal : uint - [read-only] The total size in bytes of the file
> being loaded into the application.
>

Note that this doesn't actually seem to include the amount of time to
buffer; bufferTimeMax appears to be for live streaming only (eg.
videoconferencing and webcams) to control sync, not static videos like
YouTube.

-- 
Glenn Maynard
Received on Tuesday, 18 January 2011 03:34:41 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:29 UTC