Re: [w3c/FileAPI] Proposal: `Blob.from()` for creating virtual Blobs with custom backing storage (Issue #209)

saschanaz left a comment (w3c/FileAPI#209)

Blob tries hard to be a snapshot rather than a mutable object: https://w3c.github.io/FileAPI/#blob-section

> Each [Blob](https://w3c.github.io/FileAPI/#dfn-Blob) must have an internal snapshot state, which must be initially set to the state of the underlying storage, if any such underlying storage exists. Further normative definition of [snapshot state](https://w3c.github.io/FileAPI/#snapshot-state) can be found for [File](https://w3c.github.io/FileAPI/#dfn-file)s.

Changing this may have various unexpected impact to the consumers of blobs, as @asutherland explained earlier.

Maybe we could have something like a readable version of [FileSystemWritableFileStream](https://fs.spec.whatwg.org/#filesystemwritablefilestream), which will solve the issue of postMessaging better (as streams are already postMessage-able).

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

Message ID: <w3c/FileAPI/issues/209/3959807980@github.com>