Arvid Norberg
Arvid Norberg
first draft: https://github.com/arvidn/libtorrent/pull/7831
it would be even better to coalesce announces to the same tracker (as long as it's HTTP) and use the same connection. In your case, when the trackers time out,...
I don't think this would be characterized as "spam" though. As far as I can tell from your description, all of those announces are legitimate, right?
are all or most of the announces going to the same tracker? wireshark should be able to tell you whether announces are coalesced into a single connection.
I'm hoping to do the latter. I'm pretty busy with other things right now though. Would you be interested in giving it a stab? (it's in `tracker_manager.cpp` and `http_tracker_connection.cpp`)
I don't think that is a correct characterization of how TCP congestion control works. If a TCP segment is lost, that segment needs to be re-sent, nothing else. Everyone implements...
looking into this some more, unfortunately this is not as simple as one might think. Mostly because of the current abstraction over making HTTP requests (using `http_connection`). I think the...
`router.bt.ouinet.work:6881`is the only one that appear to be working.
https://github.com/arvidn/libtorrent/pull/7827
what do you think is missing?