/ // />>/ The only issue that should be ironed out is that the rt infolet records />>/ both a failure and a success for a succesfull connection as this affects />>/ the CP rating somewhat: />>/ Consecutive Failures = 1 />>/ Connection Attempts = 1 />>/ Succesful Connections = 1 />
I'll be fixing this real soon - probably this evening. Its actually correct to count twice in the current context. What needs to happen is that we account for ip level connects in one counter and application level in another.
I tested a small stable->nio node network and it worked(!!!), so i'm guessing the problems we're having are due to that double accounting. Could you please look into it ASAP?
_______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
