Re: XML Torrents?
"Konstantin 'Kosta' Welke" <[email protected]> Sat, 12 Mar 2005 14:18:54 -0000
| Newsgroups | gmane.network.bit-torrent.general |
|---|---|
| Message-ID | <opsni3dsyse8fkrv@lydia> |
On Fri, 11 Mar 2005 16:16:30 -0800, Kenneth Porter <[email protected]> wrote: > --On Friday, March 11, 2005 8:29 PM +0000 Konstantin 'Kosta' Welke > <[email protected]> wrote: > Looking at the spec <http://www.bittorrent.com/protocol.html>, I see a > filename (or list of filename/length pairs), tracker URL, and a set of > fragment checksums. Most of the size would be the checksums. How do you > propose shrinking this to fit in a URL? I suppose you could designate > trusted peers (eg. initial seeds) to host the checksums. Olaf made a promising approach in that direction. You can take a look at http://62.216.18.38/bt_merkle/ This is also about what we expect from bt2. Theres lots of discussion going on here, centered about how to implement this idea the best way. >> bencoding is not some "binary dump" format. You can think of it as "XML >> without the bloat", i.e. Easy to parse, space-efficient, easy to extend, >> but harder to read for the human eye. > My point was just that bencoding is a Python-centric structure dump. > Data::Dumper is the Perl equivalent, and PHP also has a structure dump. Your point is wrong. bencoding was either created especially for bittorrent or has been adapted by it. It is not Pythons structure dump. Ask your favorite search engine about "python serialization" and you will find lots of pages about Pickler, but none about bencoding. Extending your search to bencoding, you will find a nice page that implements bencoding in 5 languages (4 scripting and 1 functional). Also note that bencoding is not sufficient to store a generic python object. Where did you get the idea that benconding was in any way python-specific or -centrifc? HTH, Kosta Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/BitTorrent/ <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/