Re: bencoding 0:
Mike Ravkine <[email protected]>
| Newsgroups | gmane.network.bit-torrent.general |
|---|---|
| Message-ID | <[email protected]> |
Wow, that message was so long it was flagged as spam by my ISP.
torrent meta-data files, as a general rule, will not compress as they
are composed almost entirely of hashes. Hashes, by their design, are
VERY random, and thus don't compress.
Abandoning the current simple almost-human-readable encoding scheme in
favor of a binary one (and/or adding any kind of compression) is a huge
step backwards.
--kRYPT
>[snip] So switching all the "dictionary key fields" (which are now
>transmitted as strings/text I believe... ) to "binary values" might
>save some bytes during transmission :)
>
>Well suppose one still wants to save more... then dynamic huffman
>compression could be applied... but let's not do that lol... way to
>difficult ;)
>
>If it's done... I hope a little indicator might be used to
>say: "compressed" or "uncompressed" data/stream/text if you know what
>I mean ;) so that client implementations can simply
>use "uncompressed" protocols at first as they develop... and more
>advanced implementations might used the "compressed" version of it :)
>
>Bye,
> Skybuck.
>
>
>
------------------------ Yahoo! Groups Sponsor --------------------~-->
$9.95 domain names from Yahoo!. Register anything.
http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/dkFolB/TM
--------------------------------------------------------------------~->
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/