With any BitTorrent client, you are connected to at least one tracker either a central tracker server or a distributed tracking system. The tracker stores your IP address and port, and passes it to other peers. Other clients can obtain your IP address and port from the tracker or from other peers, but may not use it right away. Your client will tell the tracker when you log off, but other clients may try to contact you before being notified about that by the tracker.
In addition, many bittorrent clients save information about active peers when stopping, and then use the stored information to speed up launch next time. Through PEX Azureus is capable of discovering peers swifter which means speedier bootstrapping to the swarm. It keep swarms together when the tracker is down and it is even able to find non-Azureus peers as long as at least one Azureus peer has a local connection to that peer , which isn't possible with the DDB alone.
Since Beta 2. AZ PEX obeys the conventions defined here. Jump to: navigation , search. Example Settings [ edit ] Peers View at Torrent Details [ edit ] The Peers screen in a torrent's details is the most important one to give you information about the reasons why the torrent download is progressing rapidly or not doing so. First fields show your interest in the peer and the peer's interest in you. Also 'snubbed' info is shown.
I usually sort the table by the downloaded data amount, as that shows the peer's importance for me. It is very typical that a major part of the data is coming from a few fast peers like it does in the example, where I have pretty much exahausted the transfer possibilities from the fastest peer, so I would expect torrent speed to decrease in near future.
Then the completion percentage and pieces graph are displayed for understanding the remaining transfer possibilities from the peer. The 22 fields used in the previous example are listed here:.
Category : Documentation. Namespaces Page Discussion. Views Read Edit View history.
0コメント