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

gabrielschulhof left a comment (w3c/FileAPI#209)

I have a use case where I'm streaming through a multipart form, including a Blob. The size is not known a priori. This is OK, because the parts each have a boundary, so the size need not be known in order to be able to stream the form back out. I use Node.js' implementation of FormData with a custom `File` class to create the form, and I stream it back out using [`FormDataEncoder`](https://npmjs.com/package/form-data-encoder). Clearly such blobs are not easily transferable, however, if we consider that they are ultimately backed by a file descriptor from which the process reads, then a mechanism can be constructed for transferring the file descriptor between processes either directly, if the platform supports this (like UNIX [`sendmsg()`](https://stackoverflow.com/questions/28003921/sending-file-descriptor-by-linux-socket), or by having one process co-operate with the other over a named pipe.

I suppose one alternative would be for the FormData API to accept `ReadableStream`s as values.

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

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