Get desktop application:
View/edit binary Protocol Buffers messages
Announces that a piece is available to other peers.
Used in:
Binary set of all pieces that peer has downloaded so far. Also serves as a handshaking message, which each peer sends once at the beginning of the connection to declare what their peer id is and what info hash they want to transmit.
Used in:
TODO: Torrent name is the content hash. Current torrent storage is content addressable. Adding name as a part of handshake makes looking up torrents faster. If storage supports addressing torrent by infohash, this extra field should removed. XXX(codyg): We rely on this name field for announcing too, so tracker can look up origins that have this content. We currently treat infohash as verification of torrents.
remoteBitfieldBytes contains the binary sets of pieces downloaded of all peers that the sender is currently connected to.
Unused.
Used in:
Notifies other peers that the torrent has completed and all pieces are available.
Used in:
(message has no fields)
General purpose error message. Receivers may check the error code to determine the origin of the message.
Used in:
Used in:
Used in:
Provides binary payload response to a peer request. Always immediately followed by a binary blob sent over socket, so the receiver should be ready to treat the blob as a non-protobuf message.
Used in:
Unused.
Unused.
Cryptographic signature of a piece content (sha1, md5).
Requests a piece of the given index. Note: offset and length are unused fields and if set, will be rejected.
Used in:
Unused.
Unused.