Hi,

Sometimes a torrent downloads oke for about ten minutes
and than becomes stalled for fifty minutes (don't know why).
If i do a manual anounce it continues downloading emediatly.
An option to change interval between anouncements would
overcomme this problem.

Also many thanks for the developers and translaters of
this very beautiful and free opensource program.

Thanks.

This is a big no-no in the BitTorrent world, every client should follow the announce time given by the tracker.

What about a "retry connection" interval? Like sometimes peers will not respond to connection one moment but later will start responding again. I find when most people discover the Update Tracker button speeds up downloads, this is the reason that it actually works -- not mainly because it actually got new peers from the tracker.

jdong wrote:What about a "retry connection" interval? Like sometimes peers will not respond to connection one moment but later will start responding again. I find when most people discover the Update Tracker button speeds up downloads, this is the reason that it actually works -- not mainly because it actually got new peers from the tracker.

We would have to keep track of all the peers we get back from the tracker. Now we just throw them away once we are done with them. We will see about this.

George wrote:

jdong wrote:What about a "retry connection" interval? Like sometimes peers will not respond to connection one moment but later will start responding again. I find when most people discover the Update Tracker button speeds up downloads, this is the reason that it actually works -- not mainly because it actually got new peers from the tracker.

We would have to keep track of all the peers we get back from the tracker. Now we just throw them away once we are done with them. We will see about this.

Is it entirely necessary to keep all the peers? or even request as many as KTorrent does? for small swarms (<20 or so I guess, maybe even larger) the request for peers doesn't need to be anywhere near 100, I believe that 50 or 30 are defaults for some clients but I'm not sure.

I don't know what information is kept for quick connect but could it be added to that? or in a similar fashion? Maybe add an option for how many peers to remember if memory is the concern, though I suppose this is another area where I need to look at the code.

Anything that increases announces to trackers, over what they are set to, risks **** people off. Manual tracker hammering is beginning to be really frowned on.

30 minutes or less, stick to it. And let the DHT or Peer Exchange work for you. If it's a private tracker that doesn't use dht, you really, really, really don't want to increase announces. Good way to get warned and banned.