<div>
fwiw I go back and forth on how I feel about this. For sure the client wants to select the mirror
</div><div>based on network performance to them. But I feel like if a mirror get's to be "stuck" and not</div><div>updating that PyPI should at some point remove it from the pool (and notify the owner that it has done so)</div><div>until it catches back up.</div>
<div></div>
<p style="color: #A0A0A8;">On Monday, April 16, 2012 at 9:30 AM, "Martin v. Löwis" wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><blockquote type="cite"><div><div>Why not go to the next level and get the script on this page to update a</div><div>DNS load balancer with all green mirrors?</div></div></blockquote><div><br></div><div>I still think that mirror selection should be on the client side. First,</div><div>if you have an infrastructure that updates the mirror list, it is again</div><div>a single point of failure. Plus, clients would want to select a mirror</div><div>based on network performance, which a DNS load balancer cannot achieve.</div><div><br></div><div>Regards,</div><div>Martin</div><div>_______________________________________________</div><div>Catalog-SIG mailing list</div><div><a href="mailto:Catalog-SIG@python.org">Catalog-SIG@python.org</a></div><div><a href="http://mail.python.org/mailman/listinfo/catalog-sig">http://mail.python.org/mailman/listinfo/catalog-sig</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>