[Bug 25081] Make read operation really async

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25081

--- Comment #29 from Arun <arun@mozilla.com> ---
(In reply to Jonas Sicking from comment #28)
> One thing that we should make sure of is that a URL object which represents
> a Blob doesn't hold the Blob data alive. As I understand it that would just
> be a waste of resources since once you do
> 
> img.src = myurlobject;
> 
> we roundtrip through a string, and so if the blob has been closed, or the
> url revoked, then the img still wouldn't load successfully. So if
> myurlobject kept the Blob data alive it would be for naught.


But the problem is if you close a Blob synchronously, or revoke the URL using
URL.revokeObjectURL,it's still possible that an asynchronous API has need of it
and that it should work. That's why parse stores the object for possible
asynchronous fetching. Of course, if it is already closed, then parse doesn't
store an object.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 23 April 2014 22:24:12 UTC