If xmlrpc obeys the HTTP standard connection limit, you're limited to 2 concurrent connections per host.<div><br></div><div>Hammering PyPi's server with more than 5 concurrent connections is also a little inconsiderate on your own part (please don't take this as an insult. Email is one-dimensional communication). I've mirrored Project Gutenberg before and they heavily rate limit people who do that: 1 connection at a time and a 2 second delay after every request.<div>
<br></div><div>-Tim Gebhardt</div><div><a href="mailto:tim@gebhardtcomputing.com">tim@gebhardtcomputing.com</a><br><br><div class="gmail_quote">On Thu, Jan 29, 2009 at 8:51 AM, Lukasz Szybalski <span dir="ltr"><<a href="mailto:szybalski@gmail.com">szybalski@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">
<br>
</div>I'm trying to download stuff from pypi via their xmlrpc. So what you<br>
are saying is I should limit the number of threads to something less<br>
then 5 and see what happens?<br>
<br>
Thanks,<br>
Lucas<br>
<div><div></div><div class="Wj3C7c">_______________________________________________<br>
Chicago mailing list<br>
<a href="mailto:Chicago@python.org">Chicago@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/chicago" target="_blank">http://mail.python.org/mailman/listinfo/chicago</a><br>
</div></div></blockquote></div><br></div></div>