Switeck Posted January 24, 2009 Report Share Posted January 24, 2009 Since a lone connection is already bidirectional and multi-purpose, why not reuse connections if the same ip is found on multiple torrents?Unfortunately handshaking and data cross-flows could be a problem, possibly making this idea not worth doing. But the purpose of this is to potentially reduce networking overheads and total connection count as well as reduce free-riding potential of a single peer gaining a bigger chunk of a seed's total upload speed and upload slots when the seed is already under a heavy load.OOPS!I actually meant for this to be in Protocol Design Discussion! Link to comment Share on other sites More sharing options...
Ultima Posted January 24, 2009 Report Share Posted January 24, 2009 Wouldn't that require support from other clients as well? Link to comment Share on other sites More sharing options...
DreadWingKnight Posted January 24, 2009 Report Share Posted January 24, 2009 It would, but if a standard handshake message can be established and the appropriate messages extended, it would be viable. Link to comment Share on other sites More sharing options...
Ultima Posted January 24, 2009 Report Share Posted January 24, 2009 Hm, so I guess this is more a call for a protocol extension than anything really µTorrent-specific, since it would benefit any client. That makes it slightly more difficult to gain traction, but I guess that didn't stop some other extensions before (or the coming uTP, for that matter ).I'm not sure the whole bandwidth/slot monopolization would really be solved unless all clients supported it though. And even then, backwards compatibility with existing clients would also hamper this extension's efficacy on that front (though I suppose that'll lessen as time goes on). Link to comment Share on other sites More sharing options...
Switeck Posted January 24, 2009 Author Report Share Posted January 24, 2009 I came up with it after reading about router exhaustion (NAT tables get filled up) due to session overloads (even at the ISP levels!) caused by BitTorrent traffic.Mentioned here:"list of reasons for needing multiple TCP connections"http://www.ietf.org/mail-archive/web/ledbat/current/msg00041.htmlhttp://www.ietf.org/mail-archive/web/ledbat/current/msg00062.htmlAnd the router connection max tests here:http://www.smallnetbuilder.com/component/option,com_chart/Itemid,189/chart,124/ Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.