It makes a bigger difference for minicpan than for cpan itself. But "fast enough" is important, and that fast enough be network relative.
Adam K On Fri, Apr 29, 2011 at 8:57 PM, Ask Bjørn Hansen <[email protected]> wrote: > > On Apr 28, 2011, at 9:19, brian d foy wrote: > >>> I think I may have implemented what you're looking for several years >>> ago for JSAN, which has a client that auto-detected appropriate >>> mirrors in a few seconds each time it starts. >>> >>> http://search.cpan.org/~adamk/Mirror-URI-0.90/lib/Mirror/YAML.pm >> >> I was looking at this, but it seems like the idea of downloading a >> small file from several mirrors isn't a good way to figure out which >> mirrors to use, especially with a large number of mirrors. > > What's the goal here? > > "Faster" is sorta dumb, really. There are few files on CPAN that are > significantly bigger that the checking for a "faster" mirror won't take > longer than just getting the file from a slower mirror. > > If it's to find a good/up-to-date mirror, then there are a couple of json > files available (on CPAN and the mirrors.cpan.org server). > > I'll talk to Henk about getting the mirrors.json file - > http://www.cpan.org/indices/mirrors.json - to include a "is this mirror > good?" flag of sorts. > > > - ask
