[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 179456] KTorrent does not allow you to pause individual torrents
From:       Adam Forsyth <agforsyth () gmail ! com>
Date:       2009-12-22 17:51:24
Message-ID: 20091222175124.E86812CC18 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=179456





--- Comment #20 from Adam Forsyth <agforsyth gmail com>  2009-12-22 18:51:20 ---
I think your argument is circular: Because we're doing things to take us out of
a state where we're an active peer, we should send not interested / choke.
However, it's the sending not interested / choking that puts us in an inactive
state to begin with. If we simply temporarily pause our data stream, we've not
done anything to remove us from an active state, so we don't need to send not
interested etc.

I also disagree that it's breaking the spec, the paused function as I wrote it
does not stop us from being ready to request chunks, which is what interested
means. The exact meaning of the wording of the spec can be argued forever, but
this follows the spirit.

The upside of remaining interested is a quicker return to normal function, and
decreased chance of peers disconnecting from us. Can you describe to me the
downside to the peer of a connection remaining interested while in between
requests, as long as at any moment it may be requesting?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]