[Bug 25081] Make read operation really async

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

Dave Herman <dherman@mozilla.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dherman@mozilla.com

--- Comment #9 from Dave Herman <dherman@mozilla.com> ---
It looks like this feature is trying to do a lot of work to make .close()
automatically race-free, but it feels awfully DWIMmy to me. The stuff here and
especially in bug 25302 sounds super complex and has me pretty concerned.

ISTM .close() is an inherently racy concept, and adding a lot of machinery to
try to defer closing won't eliminate races and will make it harder to predict
when the blob is actually closed. The straightforward semantics seems to me
that any outstanding async operation immediately fails if a concurrent .close()
happens. Then it's on the program to manage the asynchrony (which are
facilitated by features like promises, task.js, and ES7 async/await).

Dave

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

Received on Monday, 14 April 2014 22:57:46 UTC