Re: [w3c/FileAPI] Clarify Lifetime of BlobStore (#89)

Yeah, there will definitely be some kind of per-user-agent component to the blob URL store. But also a per window/worker part (or at least each entry in the global store should know which global created it, for the spec that might be easier than having separate per-global stores in addition to the global per-browser store. So indeed I'll probably I'll just end up with a single per browser blob URL store, with each entry consisting of: URL, Blob and global that created the URL (which can also be used to infer the origin of the blob URL). On "destruction" of a global I'd then just iterate over all entries revoking everything for that global. Might have to be a bit careful to make sure that navigating from the window that created a blob URL to that blob URL still works, but that's probably okay as the blob URL gets resolved before the old global goes away.

-- 
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/89#issuecomment-347488928