-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restart logic for downloading big file #18
Comments
There is (in general) the possibility to use http range request. So it should be possible to do the same here. |
Technically we could implement such a thing, but we have the danger that we mix things up. For example:
Now we have a mixup of two files, since it was modified on the server between the two downloads. |
We have eTags that get changed everytime content is modified. So workflow would be:
|
Ok, so we need to return some sort of "restartableDownload" token in the download API, which stores the file uri/size/eTag, and then can be used to resume download if it's still unchanged. In the same API change/extension, we could add async download/upload stuff to the library Patches for this will be accepted ;) |
In the 11.3.0 release we introduced the getProperties method to retrieve file/folder metadata. |
Is there any call to download the partial file from the server ?
For ex I have 1GB file and connection got lost on 800MB is there any provision to download the remaining bytes only on next call?
The text was updated successfully, but these errors were encountered: