[Bug 17262] send function should have async interface

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

--- Comment #15 from Takashi Toyoshima <toyoshim@chromium.org> 2012-06-04 09:09:43 UTC ---
> This is a separate discussion, but actually it doesn't work at all ("Block all
> writes until any already started reads finish").  The browser can't prevent
> external applications from modifying files (at least short of using mandatory
> locks, which are bad).

(notes; I'm not super familiar with FileSystem API)
In the case of FileSystem API, it's sandbox-ed and separated from native file
systems. We can assume it is not modified by external application. There is no
difference from that OS assumes disks are not modified by VMM.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 4 June 2012 09:09:47 UTC