- From: Jonas Sicking <jonas@sicking.cc>
- Date: Tue, 7 May 2013 14:54:13 -0700
- To: Glenn Maynard <glenn@zewt.org>
- Cc: Anne van Kesteren <annevk@annevk.nl>, Eric U <ericu@google.com>, Arun Ranganathan <arun@mozilla.com>, Web Applications Working Group WG <public-webapps@w3.org>
I'd be worried about letting any resolved URL to hold a reference to the Blob. We are playing very fast and loose with URLs in Gecko and it's never been intended that they hold on to any resources of significant size. / Jonas On Tue, May 7, 2013 at 1:34 PM, Glenn Maynard <glenn@zewt.org> wrote: > On Tue, May 7, 2013 at 9:45 AM, Anne van Kesteren <annevk@annevk.nl> wrote: >> >> On Mon, May 6, 2013 at 11:11 PM, Jonas Sicking <jonas@sicking.cc> wrote: >> > The only thing that's different about XHR is that the first step in my >> > list lives in one function, and the other steps live in another >> > function. Doesn't seem to have any effect on the discussions here >> > other than that we'd need to define which of the two functions does >> > the step which grabs a reference to the Blob. >> >> Fair enough. So I guess we can indeed fix this by changing >> http://fetch.spec.whatwg.org/#concept-fetch to get a reference to the >> Blob/MediaStream/... before returning early as Arun suggested. > > > Step 1 is resolve, step 3 is fetch. Moving it into step 1 means it would go > in resolve, not fetch. Putting it in fetch wouldn't help, since fetch > doesn't always start synchronously. (I'm confused, because we've talked > about this distinction several times.) > > -- > Glenn Maynard >
Received on Tuesday, 7 May 2013 21:55:12 UTC