I've updated the rate limiting downloader (that uses token bucket algorithm) to be more user friendly out of the box. It attempts to use urllib2 by default so it can rate limit pretty much any url.
Previously the script required an http proxy and the only means of adjusting operating parameters was global variables in the script. A proxy server is no longer required and all operating parameters can be adjusted via script options.
If an http proxy is selected the python http library (httplib) is used, this is a more rudimentary library so not as many situations are handled. It's possible to install a proxy handler in urllib2 but I didn't do this.
This is more-or-less a "complete" rate limiting download manager. Option output:
Usage: rlfetch.py [options] url
Options:
-h, --help show this help message and exit
-f FILE, --file=FILE output filename
-d DIR, --dest=DIR destination directory
-p SERVER:PORT, --proxy=SERVER:PORT
http proxy server
-z BYTES, --buffer=BYTES
buffer size
-l KBS, --limit=KBS kbs limit
-b KBS, --burst=KBS burst limit
-t SECONDS, --tick=SECONDS
tick interval
In locations were you have limited internet resources it's sometimes necessary to implement rate limiting. I was curious exactly how this worked so I worked out a simple Token Bucket based rate limiting HTTP downloader.
This Python script does a couple things:
Limits rate of data consumption in kilobytes per second
Prints out the instantaneous KB/s and the overal/actual KB/s [this is done by monitoring the file size on disk]
Token bucket is a pretty simple algorithm. The basic algorithm is to create an artificial stream of tokens, which are generated as fast you want to allow the real stream to go. If tokens are not removed from the "bucket" then tokens are only generated up to a "burst limit", which is the maximum amount over the average limit that's desirable (this could change to help trend a stream toward the average limit).
In the Python implementation, 3 threads are used. Thread one monitors the rate of download. Thread two consumes tokens and downloads real data from an HTTP source. Thread three generates tokens and places them in a bucket, stopping when the burst limit has been reached.