Title Could the metalink-hasher create Torrent files in the same step?
Priority wish Status resolved
Superseder Nosy List poeml
Assigned To poeml Keywords
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
to be done; it calls the "metalink" binary which is a standalone binary.
Darix suggests to look at make_torrent example from libtorrent-rasterbar and either
call that or even link libtorrent-rasterbar into metalink. That way you only need to
read each block once for hashing.
Maybe metalink could be extended easily to do the same. Or, maybe the output of
"metalink" could be used - after all, it outputs a series of hashes. However, maybe the
blocks would not fit?
Darix suggests to talk to hydri in #libtorrent.
Darix suggests as first approach to hack make_torrent calls into the python
Looking further, this is all straightforward - metalink-hasher could provide the
hashes in a form digestible by Apache, and they would contain all that's needed.
Apache could easily generated the torrent live.
However the question arises whether it might be better to have real .torrent files
on disk (and maybe even next to the original files), simply for two reasons:
For practical reasons, the latter might be more important than the former.
Links about generation of torrents:
This requires a hash cache redesign -- tracked in issue 40.
Hash cache redesign largely finished, and in testing now.
Torrent support working already in trunk. Now figuring out things like updating
the tracker servers, and exact bittorrent format that is suitable for as many
clients as possible.
another interesting link, regarding hashes to be included:
This issue can be closed as resolved. Way cool!
Date User Action Args
2010-09-05 23:45:03 poeml set assignedto: poeml
2010-09-05 23:44:56 poeml set status: testing -> resolved
messages: + msg219
2010-03-31 20:04:21 poeml set messages: + msg173
2010-03-31 19:29:05 poeml set status: deferred -> testing
messages: + msg169
2010-03-08 21:20:32 poeml set status: chatting -> deferred
2010-03-08 20:48:00 poeml set messages: + msg138
2010-02-25 00:02:38 poeml set messages: + msg134
2010-02-24 23:55:12 poeml set messages: + msg133
2010-02-04 11:43:28 poeml set messages: + msg121
2010-02-03 22:48:44 poeml set messages: + msg120
2010-02-03 22:45:30 poeml create