mirror/transmission
1
0
Fork 0
mirror of https://github.com/transmission/transmission synced 2024-12-23 00:04:06 +00:00
Code Issues Releases Wiki Activity

update ltep documentation

Browse source
This commit is contained in:
Charles Kerr 2007-09-29 23:58:37 +00:00
parent 9f926a9ca7
commit 5fa0740c27
1 changed files with 19 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
doc/extended-messaging.txt
View file

@ -11,29 +11,40 @@ sent is a handshake message, which always has an extended id of 0.
The handshake message informs the peer which extended messages are The handshake message informs the peer which extended messages are
supported and what their extended id will be. The message payload is supported and what their extended id will be. The message payload is
a bencoded dictionary which may have some of the following keys: a bencoded dictionary which may have some of the following keys:
v e
string, client name and version. eg: Transmission 0.7 int, 1 or 0. a flag to denote whether the peer prefers
p encrypted connections. This is used in ut_pex's "added.f".
int, tcp port for incoming peer connections
m m
dict containing supported extended messages and the extended id used dict containing supported extended messages and the extended id used
p
int, tcp port for incoming peer connections
v
string, client name and version. eg: Transmission 0.7
A peer may re-send the handshake message at any time to add new A peer may re-send the handshake message at any time to add new
extended message, or to disable previous messages by sending 0 as extended message, or to disable previous messages by sending 0 as
their extended id. their extended id.
µTorrent peer exchange messages use the key ut_pex in the m uTorrent peer exchange messages use the key "ut_pex" in the m
dictionary. Peer exchanges messages should be sent approximately once dictionary. If the uTorrent peer has pex disabled, this key
every minute. The payload of a peer exchange message is a bencoded will not be present. Exchanges messages should be sent approximately
dictionary with the following keys: once every minute. The payload of a peer exchange message is a
bencoded dictionary with the following keys:
added added
string, contains peers in the compact tracker format string, contains peers in the compact tracker format
(ie: 6 bytes for IPv4 address and port in network byte order) (ie: 6 bytes for IPv4 address and port in network byte order)
added since the last peer exchange message added since the last peer exchange message
added.f added.f
string, one byte of flags for each peer in the above added string. string, one byte of flags for each peer in the above added string.
according to libtorrent's ut_pex.c: according to libtorrent's ut_pex.c:
0x01 - peer supports encryption 0x01 - peer supports encryption
0x02 - peer is a seed 0x02 - peer is a seed
dropped dropped
same format as added, contains peers dropped since last peer exchange same format as added, contains peers dropped since last peer exchange
In contrast to Azureus' maximum of 50 peers per pex burst, uTorrent will
hold up to 200. alus reports: "uT stores max 200 from other peers, but it
will send everything it has."