I was wondering how to realise this part. I think I can split the problem in several smaller steps:
1) resume of a metalink download with chunk checksum. If we have chunk checksum, we can resume also a file downloaded by an other application without any other information.
2) resume of a metalink download without chunk checksum. In this case we need a log file generated by us. We can resume only "our" downloaded files.
3) resume of a web site recursively downloaded. In this case we can parse the already downloaded web pages, recovering the previous download state. In this case we don't need any log file, but we need to know filename and URL formats, so we can recover only our downloads.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
done point 1 of previous comment. Mulk is now able to resume a download using chunk checksums, thus can resume also downloads using files coming from other applications.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Not very simple to implement. I think I'll start with the resume for metalink.
I was wondering how to realise this part. I think I can split the problem in several smaller steps:
1) resume of a metalink download with chunk checksum. If we have chunk checksum, we can resume also a file downloaded by an other application without any other information.
2) resume of a metalink download without chunk checksum. In this case we need a log file generated by us. We can resume only "our" downloaded files.
3) resume of a web site recursively downloaded. In this case we can parse the already downloaded web pages, recovering the previous download state. In this case we don't need any log file, but we need to know filename and URL formats, so we can recover only our downloads.
done point 1 of previous comment. Mulk is now able to resume a download using chunk checksums, thus can resume also downloads using files coming from other applications.