(whoops, forgot to hit reply-to-all)<br><br><span class="gmail_quote"></span>Hi,<br><br>I have to say, it was never a sever problem for me, but it would make things easier. The thing is there is no point asking another dev to look into their 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 be causing another peer to dump me. It could be any number of things.
<br><br>The reason why i decided to bring this up is that despite NUnit testing and despite the fact that while testing in my localhost i sometimes get mass suicide in the peers. I'm not sure what's causing it, but all the connections will drop one after another in a very short space of time. Now i have logged all messages i'm sending/receiving and i've looked at all of em, but i don't see a problem with my own code. Therefore, how do i trouble shoot this. An error message would be nice.
<br><br>Another place where it would be useful in normal torrent downloading. ErrorMessage(19) - Being disconnected because you have sent too many bad pieces. That would be a nice stat to know because then you know you need to force a hashcheck (or something else is going wrong).
<br><br>That kinda thing.<br><br>Thanks,<br><span class="sg">Alan.</span><div><span class="e" id="q_10ecbb8ff42e18fc_2"><br><br><div><span class="gmail_quote">On 11/9/06, <b class="gmail_sendername">Adrian Ulrich</b> <
<a href="mailto:firstname.lastname@example.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">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;">Hi Alan,<br><br>> Now, the problem is this. How do i fix my client if i don't know whats
<br>> wrong? Ok, i can tool my code to log each message as it sends/receives, but<br>> that still leaves me with the problem of knowing what exactly was invalid.<br><br>But after completing the Handshake you'll know the PeerID (and software
<br>it's running). So you could ask the Author of the Client or dig into the<br>sourcecode if the peer is running a Free/OpenSource client.<br><br>I don't think it's a good idea to add extensions that will only be<br>useful while developing a client (and to be honest: I haven't run into
<br>the same problem yet while writing my own BT-client).<br>The extension would almost be useless in the 'real-world' because 95%<br>of all closed connections are caused by exiting the application or<br>timeouts.<br><br>
<br><br>> This message would be a standard peer message with a payload of a single int<br>> (or ushort if you want to conserve bandwidth). The error code in the message<br>> will link directly to a reason why the connection was terminated.
<br><br>Uh, please no magical error-codes. Make it easy: Text strings are the<br>way to go :-) (Or maybe both, like SMTP / HTTP are doing it ...)<br><br><br>I think a generic 'Message' message would be much more useful:<br>
<br><len=XX><id=Y><INT: type><INT: sequence><Message><br><br><br>type == 0 could be 'system messages/errors' / type 1 could be abused<br>for Chatting between clients (-> sequence) and maybe type 2 could be
<br>used for spamming ;-)<br><br><br>Regards,<br> Adrian<br><br><br>--<br> A. Top posters<br> Q. What's the most annoying thing on Usenet?<br>_______________________________________________<br>BitTorrent mailing list
<br><a href="mailto:BitTorrent@lists.ibiblio.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">BitTorrent@lists.ibiblio.org</a><br><a href="http://lists.ibiblio.org/mailman/listinfo/bittorrent" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">