[bittorrent] The size of XML (was: DTD for hashed files)

larytet.8708132 at bloglines.com larytet.8708132 at bloglines.com
Tue Apr 12 13:14:23 EDT 2005

--- Olaf van der Spek <olafvdspek at gmail.com wrote:
On Apr 12, 2005 5:15 PM,
Andrew Brampton <andrew at bramp.freeserve.co.uk> wrote:
> > I know this wasn't
the topic of the original posting, but I thought I'll
> > just splinter off
to provide dpmott with some "overhead numbers"
> > 
> > Using XML for the
torrent file would be bad in my opinion. The reasons being
> > are these:

> If you're going to do non-compatible changes, I'd suggest doing merkle

> trees too. Then you don't have to deal with tons of binary hashes in
your '.torrent'. Replacing the .torrent by a link would also be an
> option.

> _______________________________________________
> BitTorrent mailing list

> BitTorrent at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/bittorrent

i do not see clear advantage of merkle trees. it's nice on the paper,
but i do not see reasons to run such algorithms in the real code. what i do
right now is hash for 4MB blocks and hash for the whole file. 
Rodi design
also contains on demand hash calculation by trsuted peers (trusted peer is
one whose publis key is added to the list of trustees).
please tell me more
about merkle vs "regular" hash

More information about the BitTorrent mailing list