Re: File API: auto-revoking blob URLs

On Wed, Apr 17, 2013 at 11:58 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Mon, Apr 15, 2013 at 7:49 PM, Anne van Kesteren <annevk@annevk.nl> wrote:
>> So blob URLs are auto-revoked by default ...
>
> In https://www.w3.org/Bugs/Public/show_bug.cgi?id=19594 roc suggests
> the default cannot be changed from no auto-revoking to auto-revoking.
> (And that we'll have mediastream URLs too.) Given that, I kinda doubt
> anyone will opt into setting autoRevoke to true... We could maybe
> create a different API that does the "right thing" but then "right
> thing" has not had much interest from implementers thus far (when it
> comes to the details).

That's actually an orthogonal question to the one you raised in the
initial comment in this thread. That problem applies as long as
autorevoking URLs exist at all, independent of what the default is.

However I think that we can support autorevoking still. In gecko we
perform a "dereferencing" step where we resolve the URL against the
baseURL etc. This obviously have to happen synchronously since you
can't restart all requests if the baseURL changes. Once that step has
been performed it's safe to revoke the URL.

/ Jonas

Received on Wednesday, 17 April 2013 12:50:17 UTC