On 10/18/10 8:30 PM, Jonas Sicking wrote:
On Mon, Oct 18, 2010 at 5:17 PM, Michael Nordman<[email protected]> wrote:
Chrome currently has this as...
DOMString createBlobURL(in Blob blob);
void revokeBlobURL(in DOMString blobURL);
... no prefix... on both Window and WorkerContext.
An important aspect of placing these interfaces on the Window and
WorkerContext was to scope the lifetime of the manufactured url to the
respective window or worker object. I thought adam's url api was all about
parsing and building valid urls, so i'm not sure these methods are such a
good fit for that interface.
I agree. Another thing that is nice about the window.*BlobURL() API is
that it makes it clear which origin the created url will have. I.e.
the origin of the window which it's called on.
I agree too, and upon reflection, I'm sorry I let myself get distracted
by the URL API (but thanks anyway Anne for making me re-read it and
contemplate its future ;-)).
Renaming to createObjectURL/revokeObjectURL seems like the most
straightforward way to generify the existing methods.
I talked with Arun about this, and one argument was that we can keep
the createBlobURL name since the returned url always uses the scheme
'blob'. However I have to say that I really like the
createObjectURL/revokeObjectURL names, and it might create less
confusion.
So createObjectURL/revokeObjectURL has my vote.
Well, that's two implementers who have working prototypes of
createBlobURL and revokeBlobURL, and since you and Michael are in favor
of the name change on behalf of the implementers, that's fine by me to
rename it :). I'll make this change. Moreover, no need to hold up the
CfC on this account, since these changes are easy to make.
Future proponents of the nascent Stream API [1] can simply create
another [Supplemental] interface (or further extend the existing one) to
allow createObjectURL to take a Stream object and return a blob: URL.
So that future proofs us elegantly enough.
-- A*
[1] http://dev.w3.org/html5/html-device/#stream-api
