W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: [File API] Other sources for Blob data.

From: Glenn Maynard <glenn@zewt.org>
Date: Fri, 2 Dec 2011 18:41:42 -0500
Message-ID: <CABirCh8hqopb9vNDPGp__mQwV-pevVXO-BCZ+py4SdWyXbwpow@mail.gmail.com>
To: Steve VanDeBogart <vandebo@google.com>
Cc: public-webapps <public-webapps@w3.org>, Tony Payne <tpayne@google.com>
On Fri, Dec 2, 2011 at 6:14 PM, Steve VanDeBogart <vandebo@google.com>wrote:

> I haven't seen any other places where the javascript runtime satisfies a
> request by calling a previously called function, but in this case it seems
> like it could be done safely.
>

Hmm.  Full interoperability might be difficult, though.  For example,
different browsers might request ranges for media resources in different
ways; one browser might read the first 1K of a file first while another
might read the first 4K.  That's probably impossible to specify tightly in
general.  I'd be able to live with that, but others might object.

Another use case to consider... I was looking at this API proposal:
> http://dev.w3.org/2009/dap/gallery/#mediaobject Each media object is a
> file (a blob).  If I wanted to provide a cloud-backed gallery, I'd need
> some way to make MediaObjects for each image/song/video.  It'd be a real
> shame to have to download an object just to provide a MediaObject, which
> the consumer may or may not access.
>

I wouldn't worry much about MediaObject as a use case; it's just a poorly
designed API.  File should be a property on MediaObject, not its base class.

-- 
Glenn Maynard
Received on Friday, 2 December 2011 23:42:10 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:49 GMT