[Bug 25081] Make read operation really async

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

--- Comment #5 from Arun <arun@mozilla.com> ---
(In reply to Anne from comment #4)
> I don't see how this approach is going to work for FormData, which has
> references to a bunch of blobs it will all have to read in sequence and
> cannot deal with them being closed and probably cannot start reading them
> all at once.
> 
> I'm not entirely sure what I would do. I find the current setup rather
> weird. I would probably only have the close checks at the API-level. That
> way for FormData we can do a check once it is passed for all its associated
> blobs and if none of them is closed we can proceed with reading them all
> regardless of whether they have been closed meanwhile.


But the "current setup" is born out of trying to use the same relationship as
XHR:Fetch (that is, FileReader.readAsxx:Read Operation), as discussed!

Ok, I can definitely move the CLOSED check to API level. That way, all APIs are
responsible for internal state checking of Blobs. And read does not state
check.

-- A*

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

Received on Thursday, 20 March 2014 21:24:25 UTC