burstas / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 0 forks source link

Change Update List To Be In Sequence #142

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Possibly make the block list update function so that it will update the 
list files in sequence, rather than have them all updating at the same 
time. 

Would benefit dial-up & slow broadband users. Sometimes downloading all of 
them at the same time will cause one or more of the block-list servers to 
time out, breaking the connection.

Original issue reported on code.google.com by gary.mac...@gmail.com on 4 Oct 2009 at 10:03

GoogleCodeExporter commented 8 years ago
While I can't promise I'll get to this too quickly - according to our webstats 
the
vast majority of our users are on highspeed connections, so I consider other 
issues
higher priority - I will definitely look into it at some point.  It's actually a
nontrivial change, based on the way things are architected right now...

Original comment by peerbloc...@gmail.com on 5 Oct 2009 at 1:43

GoogleCodeExporter commented 8 years ago
If it helps, I use a PHP library that wraps a cURL multi handle to limit the 
maximum number of concurrent requests with a sliding window.

See the rolling_curl function in 
http://code.google.com/p/rolling-curl/source/browse/trunk/RollingCurl.php that 
starts around line 250.

Hopefully that's useful, because I (albeit rarely) also encounter update 
failures when too many happen at the same time - even on a 10Mbps line. To say 
my C++ knowledge is rusty would be an understatement, otherwise I'd offer a 
patch to updatelists.cpp for this.

Original comment by W.Elwoo...@gmail.com on 3 Oct 2010 at 9:55