[Bug 25081] Make read operation really async

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

--- Comment #2 from Anne <annevk@annevk.nl> ---
Okay, if throwing is always the correct thing to do (and compatible) we can do
that but then the check should not be there.

There's a bunch of scenarios.

1. send(closedBlob);
2. send(blob); blob.close();
3. send(blob); setTimeout(() => blob.close(), 0)

It seems you account for 1, but not 2 or 3. I think the way to account for 1
would actually be directly in the algorithm itself (potentially a wrapper
around the read operation if it happens often) and not the asynchronous read
operation because then you overload that operation with two distinct purposes
(sync checking of close and async reading).

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

Received on Monday, 17 March 2014 18:01:11 UTC