- From: Jonas Sicking <jonas@sicking.cc>
- Date: Mon, 18 Oct 2010 11:15:53 -0700
- To: Anne van Kesteren <annevk@opera.com>
- Cc: Arun Ranganathan <arun@mozilla.com>, public-webapps <public-webapps@w3.org>, Arthur Barstow <art.barstow@nokia.com>, Adam Barth <abarth@gmail.com>, Darin Fisher <darin@google.com>
On Mon, Oct 18, 2010 at 9:44 AM, Anne van Kesteren <annevk@opera.com> wrote: > On Mon, 18 Oct 2010 18:32:35 +0200, Jonas Sicking <jonas@sicking.cc> wrote: >> >> What would the revoking API look like? Or are you saying that there >> would be no way to get a string representation of the URL and instead >> things like img.src should accept URL objects in addition to strings? > > I am not sure what the use case for revoking is, but that method can move to > the URL object itself I suppose. (I would not want to modify everything to > also accept URL objects by the way.) Without revoking the UA has to keep around the URL-string -> resource mapping for the lifetime of the page. Which in the world of web apps can be a very long time. Even worse, in the case of dynamically created blobs (blobbuilder, canvas.toFile/toBlob/getAsFile whatever we'll call it), the resource has to stay around at least on the users file system for the lifetime of the page. / Jonas
Received on Monday, 18 October 2010 18:16:52 UTC