-
Notifications
You must be signed in to change notification settings - Fork 37
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Implement the 'Interruptable' feature #32
Comments
axel has a state file which gets updated periodically while downloading. Upon restart axel can continue from the state last saved. It would be enough to save the total file size and the remaining holes in the download to the status file. |
As an alternative to the state file approach, you could store the information in the first bytes of the downloading file, and give that file a custom file extension. The extension and download metadata would be stripped when the download completes. Here's a quick proposal for how it would work.
Limitations:
|
I think that we should try different approaches, make some bench and take the one(s) that offer the best trade-off between a fast step "Retrying the download" and a great memory usage to store current file informations (and what to download next). |
I played around with the idea I had above and built https://github.com/daveallie/grapple. I made some changes to the proposal I had earlier:
Would be happy to give a more detailed explanation of how the 'restarting' phase works if you plan to go with the process I method above. |
No description provided.
The text was updated successfully, but these errors were encountered: