<br>
<div class="gmail_quote">On Wed, Jan 20, 2010 at 7:45 AM, Robby Findler <span dir="ltr"><<a href="mailto:robby@eecs.northwestern.edu" target="_blank">robby@eecs.northwestern.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">Let me just double check something to be sure I'm on the same page.<br>The planet mirror will completely avoid the current planet server,<br>
right? So, it has to be able to make the decision: given a planet<br>package request (including the version number of the mzscheme loading<br>the package) and the information on the mirror, which package to<br>serve, right?<br>
</blockquote>
<div><br>Yes - the planet proxy/mirror has the same decision logic (sans bugs) that I have observed from the current planet server externally, so once a package is downloaded it can avoid hitting the planet server again. </div>
<div> </div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">I'm thinking you don't want to duplicate that code, right? Do you have<br>a plan for that? One thing would be for you to actually run a planet<br>
server on the mirror, no?<br></blockquote>
<div><br>I agree that generally it's better not to duplicate code. In this case I built the proxy/repo (and add the mirror/crawler in the next release) as a proof of my bzlib/* framework, so the duplication is currently intentional (a part of my plan was to test the framework). <br>
<br>The proxy/mirror is currently only for planet client consumption instead of human, so it is not a verbatim planet server clone. But building on top of bzlib/shp will allow me to extend that way as well. <br><br>It would be interesting to see if the two can/should be merged/collaborated in the future. That is if you are interested of course ;)<br>
<br>Also - thanks for exposing the archives link - that's exactly what I was looking for. Appreciated.<br><br>Thanks,<br>yc<br><br></div>
</div>