- From: Feras Moussa <ferasm@microsoft.com>
- Date: Wed, 7 Mar 2012 23:58:02 +0000
- To: Anne van Kesteren <annevk@opera.com>, Arun Ranganathan <aranganathan@mozilla.com>
- CC: Adrian Bateman <adrianba@microsoft.com>, "public-webapps@w3.org" <public-webapps@w3.org>, Ian Hickson <ian@hixie.ch>
> -----Original Message----- > From: Anne van Kesteren [mailto:annevk@opera.com] > Sent: Wednesday, March 07, 2012 12:49 AM > To: Arun Ranganathan; Feras Moussa > Cc: Adrian Bateman; public-webapps@w3.org; Ian Hickson > Subject: Re: [FileAPI] Deterministic release of Blob proposal > On Wed, 07 Mar 2012 02:12:39 +0100, Feras Moussa <ferasm@microsoft.com> > wrote: > >> xhr.send(blob); > >> blob.close(); // method name TBD > > > > In our implementation, this case would fail. We think this is > > reasonable because the need for having a close() method is to allow > > deterministic release of the resource. > > Reasonable or not, "would fail" is not something we can put in a standard. > What happens exactly? What if a connection is established and data is being > transmitted already? In the case where close was called on a Blob that is being used in a pending request, then the request should be canceled. The expected result is the same as if abort() was called.
Received on Wednesday, 7 March 2012 23:58:38 UTC