Will this use the FileReader to read?

[PaulKinlan]

I would expect the API to prefer to use the File and FileReader API rather than a new custom read function.

[drufball]

I agree though that we'll want to reuse API's wherever possible. These are mostly just strawmen API ideas, rather than what I expect the final API to use. @inexorabletash @cmumford thoughts?

[kenchris]

Or maybe something like https://streams.spec.whatwg.org/#rs-class ReadableStream

[inexorabletash]

I assume we'll use File if possible. And while I'd love File to grow more usable reading methods like Request/Response's Body that's probably out of scope, so I would assume File/FileReader are there.

[inexorabletash]

One plausible API sketch is here: https://gist.github.com/petkaantonov/37a9c64ea2bbd1aa3ca5

[addyosmani]

I assume we'll use File if possible. And while I'd love File to grow more usable reading methods like Request/Response's Body that's probably out of scope, so I would assume File/FileReader are there.

This sounds like a reasonable start to me.

[mkruisselbrink]

Current proposal does in fact use File/FileReader for reading. That already gives you somewhat hacky integration with ReadableStreams (i.e. you can wrap a File in a Response to get a ReadableStream backed by the file via new Response(blob).body). Possibly we should get a less hacky way of doing that, but that would be w3c/FileAPI#40 anyway.