- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Tue, 27 Aug 2013 15:30:10 +0200
- To: public-media-capture@w3.org
On 08/27/2013 01:05 PM, Anne van Kesteren wrote: > On Tue, Aug 27, 2013 at 11:27 AM, Harald Alvestrand > <harald@alvestrand.no> wrote: >> Thanks for the advice! >> Would that be the same as sending a note to the editors asking that the URL >> >> http://dev.w3.org/2006/webapi/FileAPI/#creating-revoking >> >> be kept as a stable reference, because we want to refer to it? >> I'm not sure what a "hook in the File API specification" actually means. > No, the algorithms defined in > http://dev.w3.org/2006/webapi/FileAPI/#creating-revoking would have to > be parameterized somehow. So they make sense for Blob, but also for > other objects that are Blob-like. And then I guess in your > specification you would end up with the createObjectURL() overload and > a sentence that says "MediaStream is a Blob-like" and then everything > else would follow from that. > > OK, I see (I think). There are a couple of things that have to be removed from FileAPI section 11 to make it parameterizable to MediaStream objects - in particular, the "Dereferencing model for Blob URIs" simply doesn't make sense in this context. Do you think the File API editors would be sympathetic to making the necessary changes?
Received on Tuesday, 27 August 2013 13:29:45 UTC