geh Posted July 21, 2008 Report Share Posted July 21, 2008 Hi there,my request is the following: could you add an advanced option for manually setting a tcp keepalive timeout? The reason is that my ISP (university) cuts all connections for which no data is sent for more than 1 (one) minute. So I can have 300 peers but may be connected to only half a dozen or so at a time.Thanks for considering! Link to comment Share on other sites More sharing options...
Firon Posted July 21, 2008 Report Share Posted July 21, 2008 There's already keep-alive messages in the protocol itself. Using TCP keep-alives is unnecessary. Link to comment Share on other sites More sharing options...
geh Posted July 22, 2008 Author Report Share Posted July 22, 2008 You are right, but it was not my point. Hm, I have to make myself more clear...What I want is either an option to enable tcp keep-alives, or an option to set the application level keep-alive timeout. Both would work for me.[rationale: tcp keep-alives cannot be configured with app specific timeout values, but it is possible to adjust the system wide setting, so just enabling tcp keep-alives would work. setting tcp keep-alives for sockets is trivial that is why I requested it first hand. application level keep-alive timeouts are also not hard to implement but requires to set up timers manually. ]Thanks again! Still hoping for one or the other option to be implemented so I can connect to all the other peers, too! )Bye... Link to comment Share on other sites More sharing options...
thelittlefire Posted July 23, 2008 Report Share Posted July 23, 2008 It's based in the protocol. Given the maintainers of the protocol control uTorrent, changes to the protocol WILL NOT be implemented in the client without referral/approval/perusal at http://bittorrent.org/beps/bep_0000.html Link to comment Share on other sites More sharing options...
geh Posted July 23, 2008 Author Report Share Posted July 23, 2008 Sending keep-alives within certain time frames does NOT mean a change to the spec. The spec does not restrict, nor does it oblige any specific algorithms for when to send keep-alive messages. Regarding tcp keep-alives, that does not even touch the bittorrent protocol.---Hi again,after an analysis of the utorrent peer wire protocol traffic I figured that utorrent uses a 2 minute app level keep-alive timeout. This means that the functionality is already there, and providing users a possibility to change this timeout value is merely a matter of providing an option for this in the user interface.I don't know who decides which feature requests get forwarded to the developers, or if developers read the forums themselves, but it would be really great if this could be implemented. Of course, if it is dismissed because I'm the only one requesting it I'll accept. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.