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.<br><br>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).
<br><br>Alan.<br><br><div><span class="gmail_quote">On 11/10/06, <b class="gmail_sendername">Thad Ward</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, Nov 09, 2006 at 07:59:10AM +0000, Alan McGovern wrote:<br>><br>> I have to say, it was never a sever problem for me, but it would make things<br>> easier. The thing is there is no point asking another dev to look into their
<br>> source code as i already know quite a few cases where a connection would<br>> just be dropped. The problem is i don't know which one it is that would be<br>> causing another peer to dump me. It could be any number of things.
<br><br>You could take the source and add your own debugging code to log out why<br>it is dropping the connection (ie, which case is being hit, what it was<br>expecting, what it got, etc).<br><br>---<br>Thad Ward<br>_______________________________________________
<br>BitTorrent mailing list<br><a href="mailto:BitTorrent@lists.ibiblio.org">BitTorrent@lists.ibiblio.org</a><br><a href="http://lists.ibiblio.org/mailman/listinfo/bittorrent">http://lists.ibiblio.org/mailman/listinfo/bittorrent