Class RubyTorrent::PeerConnection
In: lib/rubytorrent/peer.rb
Parent: Object

The PeerConnection object deals with all the protocol issues. It keeps state information as to the connection and the peer. It is tightly integrated with the Controller object.

Remember to be "strict in what you send, lenient in what you accept".

Methods

cancel   choke=   dlamt   dlrate   have_piece   last_recv_block_time   last_recv_time   last_send_block_time   last_send_time   new   peer_complete?   pending_recv   pending_send   piece_available?   send_blocks_and_reqs   send_keepalive   shutdown   snub=   start   start_time   to_s   ulamt   ulrate  

Included Modules

EventSource

Constants

BUFSIZE = 8192
MAX_PEER_REQUESTS = 5
MAX_REQUESTS = 5
MIN_REQUESTS = 1
REQUEST_TIMEOUT = 60

Attributes

name  [R] 
peer_pieces  [R] 

Public Class methods

new(name, controller, socket, package)

decide it‘s been forgotten

Public Instance methods

cancel(block)

called by Controller in the event that a request needs to be rescinded.

choke=(now_choke)

the Controller calls this from heartbeat thread to tell us whether to choke or not.

have_piece(piece)

Controller calls this to tell us that a complete piece has been received.

send_blocks_and_reqs(dllim=nil, ullim=nil)

this is called both by input_thread_step and by the controller‘s heartbeat thread. it sends as many pending blocks as it can while keeping the amount below ‘ullim’, and sends as many requests as it can while keeping the amount below ‘dllim’.

returns the number of bytes requested and sent

send_keepalive()

Controller calls this to tell us to send a keepalive

snub=(now_snub)

the Controller calls this from heartbeat thread to tell us whether to snub or not.

[Validate]