![]() Registered Member ![]()
|
(was having trouble creating an account, so this is redundant with an email)
ktorrent (2.0.2) snubs only seed (???) In a torrent which is initial seeding, ktorrent seems quite happy to choke, and afterwards (??) snub the only seed who has data available. I understand the choking, although it seems overeager to do so when the incoming data is far below the observed maximum. However, snubbing a peer which is already choked does not not seem understandable to me. In any event, the net result is that ktorrent is not an assistive member of an initial seed situation, acting only as a data sink, not as a data retransmitter. |
![]() Registered Member ![]()
|
|
![]() Moderator ![]()
|
|
![]() Registered Member ![]()
|
Correct me if I'm wrong, but the Choked field indicates whether or not the remote peer has choked you, right?
Also, snubbed is just an indication by your client that the peer has not sent any data to you in 60 seconds... but it does not block the peer from sending you more data, right? |
![]() Registered Member ![]()
|
Huh, it seems the display of attributes across a range of bittorrent clients is not completely consistent in terms of similar names meaning identical things. I guess that's no shock.
I was surprised to find nothing in the logging that had to do with the ongoing transfers with existing peers. |
![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
Choked means that the peer has choked YOU, so you cannot download from the peer. IT doesn't mean you can't upload to that peer -- in fact, uploading more to that peer will increase the chances of that peer unchoking you. |
![]() Moderator ![]()
|
No, there was a feature in the fast extensions which would allow you to download a couple of select chunks from a peer who has choked you. This feature has mysteriously dissappeared from the standard. |
Registered users: Bing [Bot], blue_bullet, Google [Bot], rockscient, Yahoo [Bot]