[Question] Channels download.delete and download.createReadStream

[kblok]

I realized that download.delete is using a channel to delete the file. I thought that it would make sense if we'd have a remote server. The file would be in the server, not in the client.

But then I found that download.createReadStream is solving everything on the client-side. I think this is quite inconsistent. Or we address everything on the server (getting ready for a remote server), or we solve file manipulation on the client.

[kblok]

Thoughts @pavelfeldman?

[aslushnikov]

@kblok feel free to ping us on slack :-) I'll close the issue here.

[dgozman]

With #3634, we now have:

• download.path works locally and throws in remote scenario;
• download.delete always deletes on the server;
• download.createReadStream streams bytes from the local file or remote server;
• download.saveAs copies a file when running locally or uses saveAsStream to stream bytes from remote server to save locally.

Feel free to ask more questions.