- From: <bugzilla@jessica.w3.org>
- Date: Fri, 01 Jun 2012 07:51:02 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17262 --- Comment #7 from Jonas Sicking <jonas@sicking.cc> 2012-06-01 07:51:02 UTC --- Blobs are very intentionally read-only. It's part of their design. We can rely on the fact that no interfaces will be introduced in the future to make them mutable. For something like a FileSystem API, if the "underlying" data changes the FileSystem API needs can deal with this in many ways: * Neuter the blob such that any reads from it will fail * Use a copy-on-write scheme such that any already existing Blob objects maintain their values (this would likely be prohibitively expensive though). * Block all writes until any already started reads finish * Block all writes until all Blob references to the data go away. This is up to the FileSystem API to define. For what it's worth I believe the FileSystem spec proposed by google uses the first bullet above. The FileHandle API proposed by mozilla uses the third. -- 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 Friday, 1 June 2012 07:51:05 UTC