[bittorrent] Protocol Deviation in Mainline
Olaf van der Spek
olafvdspek at gmail.com
Thu Mar 2 04:58:41 EST 2006
On 3/2/06, Elliott Mitchell <ehem at m5p.com> wrote:
> >From: Olaf van der Spek <olafvdspek at gmail.com>
> > On 3/2/06, Elliott Mitchell <ehem at m5p.com> wrote:
> > > I'm guessing the most likely reason is to allow other messages more often
> > > and therefore keep a more accurate picture of the swarm. This though is
> > > spurious reasoning, you're still likely to continue in progress pieces.
> > > Could be the desire is to more precisely tit-for-tat, but this is also
> > That's the reason uau mentioned.
> > > spurious because on any links you're going to transfer a lot more than
> > > 32KB in one choke-period (10 seconds) so the increased precision simply
> > > get overwhelmed. Even the old 32KB is small compared to most files being
> > > transfered and bandwidth, why cap at 16KB? (I can't see it doing anything
> > > but breaking compatibility)
> Ouch, bad place to inline that statement. I'm guessing you were refering
> to the second?
Yes (and to the sentence directly above).
> So, two questions: First, does (if so, how?) this help?
I've no idea.
> Second, is this
> worth misbehaving and violating the protocol specification?
More information about the BitTorrent