Ticket #896 (new enhancement)
Finished, but incomplete; Manually Triggering on_finished, react smartly
| Reported by: | lostnihilist | Owned by: | rakshasa |
|---|---|---|---|
| Priority: | low | Component: | libtorrent |
| Version: | Severity: | minor | |
| Keywords: | Cc: |
Description
The current system for dealing with completed files is not yet complete, in my opinion.
Case 1) (Higher Priority) User does not want to download all the files:
Perhaps a fourth option in the files menu could be added: "no" in the toggle between normal, off, and high. Only it should require a special key sequence instead of being within the typical toggling cycle, perhaps with an "are you sure" warning. This would indicate that the user has no intention of downloading the file. Rtorrent would then unlink the file (aka delete it) and then if all the other files (excepting other "no" files) are completed, would register the torrent has having been finished. I don't know the bittorrent protocol, so I'm not sure how this would impact the &left=xbytes response to the tracker.
Case 2) (Lower Priority) Large torrent, user wants to see files as they come in
Currently, the entire torrent has to be completely downloaded for the user to see it show up as .finished using the new features. What would be interesting if there was an option such that the directory tree was replicated with the .finished symlinks in a specific directory. Directories would not be symlinked until at least one file inside the directory was fully downloaded.
I request these because I want to make a script (probably a bit of python with inotify) that will watch for those .finished symlinks and then create hard-links in a user specified directory. Then, when the user removed the torrent, it would unlink the original file and delete the symlink. Clearly this has some drawbacks (e.g. the finsihed directory needs to be on the same drive). But I think its the best way of going about it unless rtorrent intends to have a more complete finished directory feature.
