From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Dave Page <dpage(at)pgadmin(dot)org>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RFC: PostgreSQL Add-On Network |
Date: | 2010-01-08 18:18:45 |
Message-ID: | 4B477705.4010900@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander wrote:
> On Fri, Jan 8, 2010 at 18:48, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>> 2010/1/8 Magnus Hagander <magnus(at)hagander(dot)net>:
>>> On Fri, Jan 8, 2010 at 18:44, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>>> The current set of active mirrors can always be found at
>>>> http://www.postgresql.org/mirrors.xml, so you can build URLs on the
>>>> mirror network using the protocol, host, port and path from the mirror
>>>> list, and then the relative path for the file.
>>> Or you can hit it off the mirror redirector on the website, which will
>>> then give you automatic download tracking.
>> Right, but you need the mirror ID for that iirc. Maybe we should add
>> that to the XML...
>
> That, or implement that "send me to a random mirror" feature. Or
> maybe the "send me to a random close mirror if available, or a random
> global if not" feature. :-)
>
> Either way, there's definitely room for some improvement there, but
> let's figure out what the exact needs are first :-)
well we could fairly trivially do that using DNS as well as in providing
sets of mirrors geographically spread out (like
us.mirrors.postgresql.org, eu.mirrors.postgresql.org) or whatever.
Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2010-01-08 18:19:31 | Re: Listen / Notify - what to do when the queue is full |
Previous Message | Andres Freund | 2010-01-08 18:13:49 | Re: damage control mode |