W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2009

[whatwg] autobuffer on "new Audio" objects

From: Nils Dagsson Moskopp <nils-dagsson-moskopp@dieweltistgarnichtso.net>
Date: Mon, 20 Jul 2009 07:06:32 +0200
Message-ID: <1248066392.22900.48.camel@desudesudesu>
Am Montag, den 20.07.2009, 05:46 +0100 schrieb David Wilson:
> It's easy to see how some naively implemented JS audio widget could
> fetch 200mb over an expensive 3G connection, simply by navigating to
> some site in a background tab (say, by creating an array of elements
> to represent their playlist - something I'd have thought was perfectly
> valid behaviour).

I second that motion, not only as owner of a smartphone, but also as
someone with webspace that has a volume cap. Automagic audio element
buffering could deter web authors from dynamically putting more than one
element on a page, thus reserving javascript playlist widgets to those
who can afford more bandwith on an order of magnitude (!).

I believe the burden of writing another line should solely be on those
who want autobuffering, to prevent unneccessary bandwith consumption.

Cheers
-- 
Nils Dagsson Moskopp
<http://dieweltistgarnichtso.net>
Received on Sunday, 19 July 2009 22:06:32 UTC

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