[bittorrent] Proposed Extension to Peer Protocol
alan.mcgovern at gmail.com
Sun Nov 12 09:15:08 EST 2006
Well, i suppose i could, but i wouldn't consider myself able to hack
together debugging code for those kind of specific situations in java, c,
c++ or vb.
There are legit cases where these messages would prove useful in real-world
usage. Suppose i send a peer piece 16 of a torrent, and it turns out to be
corrupt on their end. Wouldn't it be nice if that peer sent a message back
to me saying that the piece was corrupt? Then i could run my own hashcheck
on it and (optionally) resend it (assuming the peer sends a new request for
it to me).
On 11/10/06, Thad Ward <coderjoe at grnet.com> wrote:
> On Thu, Nov 09, 2006 at 07:59:10AM +0000, Alan McGovern wrote:
> > I have to say, it was never a sever problem for me, but it would make
> > easier. The thing is there is no point asking another dev to look into
> > source code as i already know quite a few cases where a connection would
> > just be dropped. The problem is i don't know which one it is that would
> > causing another peer to dump me. It could be any number of things.
> You could take the source and add your own debugging code to log out why
> it is dropping the connection (ie, which case is being hit, what it was
> expecting, what it got, etc).
> Thad Ward
> BitTorrent mailing list
> BitTorrent at lists.ibiblio.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the BitTorrent