For a 256kB file, 0101 would mean that the 2nd and 4th chunk had been completely downloadedġ 2 3 |-|-|-| 1: 32-bit number holding the number of 64kb chunks 2: n bits holding bit flags for each chunk 3: File contents The next n bits were bit flags representing if the relevant chunk had been downloaded.The first 32 bits would be a 32-bit integer that represented the number of 64kB chunks in the file.
The changes I proposed to get the feature working were as follows: If the download was interrupted, there was no way to determine how much of the file each thread had downloaded so all threads had to start from the beginning of their section. Start n threads at even intervals of the file and have each of the threads download its section. The way Snatch worked was to first pre-allocate the space needed to download the file.
I formalised my thoughts for how I believed the feature should be written and wrote up a draft proposal for it in the open issue for interruptablilty in the repo. I opened an issue, wrote a PR to fix it, and gave a bit more thought to the feature. I tried to get comfortable with the codebase to see if writing in the interruptable feature would be difficult. How can you have an interruptable download accelerator, without the interruptable part?! Proposing Interruptablity The Interruptable feature is not implemented yet.
0 kommentar(er)
