Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Could the metalink-hasher create Torrent files in the same step? #31
Issue migrated (2015-06-05) from old issue tracker http://mirrorbrain.org/issues/issue37
msg119 (view) Author: poeml Date: 2010-02-03.22:45:30
Vittorio suggested that the metalink-hasher might create torrent files along the way.
The metalink-hasher is a Python program which walks the file tree and looks what needs
Darix suggests to look at make_torrent example from libtorrent-rasterbar and either
Maybe metalink could be extended easily to do the same. Or, maybe the output of
msg120 (view) Author: poeml Date: 2010-02-03.22:48:44
Darix suggests to talk to hydri in #libtorrent.
msg121 (view) Author: poeml Date: 2010-02-04.11:43:28
Darix suggests as first approach to hack make_torrent calls into the python
msg133 (view) Author: poeml Date: 2010-02-24.23:55:12
Looking further, this is all straightforward - metalink-hasher could provide the
However the question arises whether it might be better to have real .torrent files
For practical reasons, the latter might be more important than the former.
msg134 (view) Author: poeml Date: 2010-02-25.00:02:38
Links about generation of torrents:
msg138 (view) Author: poeml Date: 2010-03-08.20:48:00
This requires a hash cache redesign -- tracked in issue 40.
msg169 (view) Author: poeml Date: 2010-03-31.19:29:03
Hash cache redesign largely finished, and in testing now.
Torrent support working already in trunk. Now figuring out things like updating
msg173 (view) Author: poeml Date: 2010-03-31.20:04:21
another interesting link, regarding hashes to be included:
msg219 (view) Author: poeml Date: 2010-09-05.23:44:55
This issue can be closed as resolved. Way cool!
(end of migrated issue)