You should probably do a one-time request (per week/month, whatever fits). for each feed and follow redirects to get the "true" address. Regardless of your throttling situation at the time, you should be able to resolve all feeds, save that data and then just do it once for every new feed you add to the list. You can look at urllib s geturl() as it returns the final url from the URL you put into it. When you do ping the feeds, be sure to use the original (keep the "real" simply for load-balancing) to make sure it redirects properly if the user has moved it or similar.

Once that is done, you can simply devise a load mechanism such as only X requests per hour for a given domain, going through each feed and skipping feeds whose hosts have hit the limit. If feedburner keeps their limits public (not likely) you can use that for X, but otherwise you will just have to estimate it and make a rough estimate that you know to be below the limit. Knowing google however, their limits might measure patterns and not have a specific hard limit.

Edit: Added suggestion from comment.

If your problem is related to Feedburner "throttling you", it most certainly does this because of the source IP of your bot. The way to "load balance to Feedburner" would be to have multiple different source IPs to start from.

Now there are numerous ways to achieving this, 2 of them being:

1. Multi-homed server: multiple IPs on the same machine
2. Multiple discrete machines

Of course, don t you go a put a NAT box in front of them now ;-)

The above takes care of the possible "throttling problems", now for the "scheduling part". You should maintain a "virtual scheduler" per "destination" and make sure not to exceed the parameters of the Web Service (e.g. Feedburner) in question. Now, the tricky part is to get hold of these "limits"... sometimes they are advertised and sometimes you need to figure them out experimentally.

I understand this is "high level architectural guidelines" but I am not ready to be coding this for you... I hope you forgive me ;-)

"how can I load balance outgoing requests so that I don t hit any one host too often?"

Generally, you do this by designing a better algorithm.

For example, randomly scramble your requests.

Or shuffle them fairly so so that you round-robin through the sources. That would be a simple list of queues where you dequeue one request from each host.