mapa17/Eruliaf — Issue #36: Correct un/chok algorithm
Author: mapa17
Created: 2012-03-04 15:26:53+00:00
State: open
Labels: Bug, nodes, Refactoring, Todo

The un/chok algorithm is broken, or not implemented correctly.

How it should behave:

TFT: unchok peers that have a high upload rate even they are not interested in our pieces
if both peers are in state unchok, send data
Limit the number active transfers to maxTFTSlots

OU: unchok interested! peers randomly

Situtaion:
We unchok a node that has a high upload rate but is not interested in our data. In the future we get an interesting
piece, so the peer will change to interested and to unchok as well. We will have to evaluate the number of free maxTFTSlots and if there is no free Slot if to accept the new peer and chok and old one or not.