On Tue, Sep 7, 2010 at 12:57 AM, Nicolas Pitre <nico@xxxxxxxxxxx> wrote: > But I think that Luke has enough > to play with already by only assuming the easy case for now. um, yes. i only just noticed that bittorrent's multi-file mode has blocking that doesn't line up with the bloody file beginnings and ends: | block 0 256k | block 1 256k | block N 11bytes | |file1 | file2 | file3 | file4 | this is why cameron dale threw his hands up in horror at bittorrent when he created debtorrent, but i didn't understand why, fully, as i thought that he was creating one .torrent per .deb _anyway_ so if he had it would have been moot. so i have to do some tests to see if multiple individual torrents can be added using the BitTornado API to the same server, and redesign the damn code so that it adds new "files" to be downloaded based on the previous one completing. so, the first quotes file quotes to be requested will be the "rev-list", and the "finished" callback function will result in the next layer of "files" as .torrents to be requested, and then finally the files representing the actual "objects" - generated as git cat-files on the remote end - get added and requested. so - all event-driven. eek! fuun. about as understandable as nmbd in samba (*) :) l. (*) i can say that because i did its 1st major rewrite ha ha -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html