3 ms·
Hijacking this thread for a download question. Currently, to download a file you click on the link and the browser pushes the data to the native (not sandboxed
by deskamess 11y ago
Hijacking this thread for a download question.
Currently, to download a file you click on the link and the browser pushes the data to the native (not sandboxed) file system. Your code does not see any of the data.
Instead of an automated download, is there a way, on a user initiated download request to just get a handle to a native file (not sandboxed) and populate the native file yourself. Ideally we could then implement a faster download with multiple range requests against multiple storage end points. Or make other custom browser side transformations on the data.
- saurik 11y agoWhy can't you do these things against a sandboxed file, and then move the file at the end of the download out of the sandbox? Isn't this in fact exactly what Mega does?
- deskamess 11y agoI am not sure what mega does... is their source open? I guess I should just try it. My concerns were having a large enough sand box (files could be 1G+, and many of them) and if there is, even for a short time, a 2x storage hit. Then the second hit of copying (not moving) from sandbox to local or remote drive.