Changeset 11075

Show
Ignore:
Timestamp:
05/13/2008 05:02:55 PM (6 months ago)
Author:
dave
Message:

Fix references.

Location:
dotorg/trunk/html/beps
Files:
2 modified

Legend:

Unmodified
Added
Removed

  • dotorg/trunk/html/beps/bep_0023.rst

    r11070 r11075  
    2222======== 
    2323 
    24 In BitTorrent as described in BEP 3 [#BEP-3], peers wishing to 
     24In BitTorrent as described in BEP 3 [#BEP-3]_, peers wishing to 
    2525transfer a file contact a central tracker.  This tracker returns a 
    2626list of peers that are currently transferring the file.  The list of 

  • dotorg/trunk/html/beps/bep_0024.rst

    r11069 r11075  
    2424through the public Internet. 
    2525 
    26 In BitTorrent as described in BEP 3 [#BEP-3], peers wishing to 
     26In BitTorrent as described in BEP 3 [#BEP-3]_, peers wishing to 
    2727transfer a file contact a central tracker.  This tracker returns a 
    2828list of peers that are currently transferring the file.  For all peers 
    … …  
    4747address.  Any peer reached over the public Internet sees the public IP 
    4848address of the peer on the far side of the connection.  The *Extension 
    49 Protocol* proposed in [#BEP-10] provides a mechanism for a client to 
     49Protocol* proposed in [#BEP-10]_ provides a mechanism for a client to 
    5050obtains its public IP from any of its peers.  There is no conflict for 
    5151a BitTorrent client to support both tracker and peer methods, and they 
    … …  
    5353from a tracker even when there are no peers.  For trackerless swarms, 
    5454a peer can learn its IP from any peer whose reference was obtained from the DHT 
    55 [#BEP-5]. 
     55[#BEP-5]_. 
    5656 
    5757