Show
Ignore:
Timestamp:
02/06/2008 10:01:00 AM (11 months ago)
Author:
arvid
Message:

updates to make file to refer to the tempalte.txt. Fixed broken links in bep 0000. Updated wording and added references to metadata extension. Fixed layout of bep 0004

Files:
1 modified

Legend:

Unmodified
Added
Removed

  • dotorg/trunk_fixed/html/beps/bep_0009.rst

    r10528 r10561  
    2323part of the .torrent file is referred to as *the metadata*. 
    2424 
    25 The metadata is plit up in 16kiB pieces. The pieces are indexed starting 
    26 from 0 for the first 16kiB of metadata. 
     25The metadata is handled in bocks of 16KiB (65536 Bytes). The metadata blocks 
     26are indexed starting at 0. All blocks are 16KiB except the last block which may 
     27be smaller. 
    2728 
    2829extension header 
    2930================ 
    3031 
    31 The metadata extension uses the `extension protocol`_ to advertize its 
    32 existence. It adds the "ut_metadata" entry to the "m" dictionary in the 
    33 extension header hand-shake message. This identifies the message code 
    34 used for this message. It also adds "metadata_size" to the handshake 
    35 message (not the "m" dictionary) specifying an integer value of the 
     32The metadata extension uses the extension protocol (specified in `BEP 0010`_ 
     33) to advertize its existence. It adds the "ut_metadata" entry to the "m" 
     34dictionary in the extension header hand-shake message. This identifies the 
     35message code used for this message. It also adds "metadata_size" to the 
     36handshake message (not the "m" dictionary) specifying an integer value of the 
    3637number of bytes of the metadata. 
    3738 
    38 .. _`extension protocol`: extension_protocol.html 
     39.. _`BEP 0010`: http://www.bittorrent.org/beps/bep_0010.html 
    3940 
    4041Example extension handshake message:: 
    … …  
    120121 
    121122<info-hash> 
    122         Is the info-hash encoded as base32. 
     123        Is the info-hash encoded as base32 [#base32]_ 
    123124 
    124125``xt`` is the only mandatory parameter. ``dn`` is the display name that may be 
    … …  
    129130Both ``dn`` and ``tr`` are optional. 
    130131 
    131 If no tracker is specified, the client SHOULD use the DHT to acquire peers. 
     132If no tracker is specified, the client SHOULD use the DHT (`BEP 0005`_) to acquire peers. 
    132133 
     134.. [#base32] http://www.ietf.org/rfc/rfc3548.txt 
     135.. _`BEP 0005`: bep_0005.html 
    133136 
    134137