Re: [w3c/FileAPI] Blob URL store partitioning (#153)

An upside of limiting Blob URL's to agent clusters is that it limits the potential for browser compat issues related to races for resolving Blob URLs against the Blob URLs being revoked.  Right now [resolve a Blob URL](https://w3c.github.io/FileAPI/#blob-url-resolve) references the [Blob URL Store](https://w3c.github.io/FileAPI/#BlobURLStore) like it's something that's synchronously accessible across all agent clusters.  (I believe this leads to the situation described in https://github.com/w3c/FileAPI/issues/157 where Chrome has to use sync IPC when creating Blobs.)

That could alternately be addressed by specifying Blob resolution and Blob URL Store manipulations in a more multi-process way.  The previously referenced https://github.com/w3c/FileAPI/issues/157 would likely entail this because of the integration with storage.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/153#issuecomment-868877343