Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Why do you think this is a problem?

    Letting CPAN.pm configure itself with sensible defaults is a good thing - it creates a better user experience, and if for whatever reason you want to use a specific mirror it can easily be set using the "o conf urllist" command.

    • CPAN appears to take real pride in the fact that it has a huge network of 222 mirrors. Is that pride justified? Or is having such a network of mirrors just an outdated (1995), almost ridiculous concept?

      • I doubt whether anybody still modifies the default settings for CPAN.pm, once it works. I know I don't. That means that currently maybe say 70% of all installations use the same 3 or 4 repository servers, and that percentage can only just go up.

        Do we really have to maintain the mirror network? Or can we think of dismantling it? You could argue that, now it works, that keeping the mirror network running comes at no cost at all. Fine.

      • If it is still useful to have this huge network of mirrors, then we maybe we ought to spread the load, automatically.

        BTW I noticed the other day that http://cpan.strawberryperl.com/ [strawberryperl.com] automatically forwards to http://cpan.yahoo.com/ [yahoo.com], probably a server that is more up to the heavy load of supporting everybody on the planet. Running a repository for the whole planet may have proven not to be trivial, after all.

      But my earlier idea of setting up a webservice for the mirror list may actually be a far more complicated solution than necessary. Perhaps it suffices if people's CPAN clients would just round-robin in the list of mirrors in their (sub-)continent, or each time, randomly pick a mirror from that same list.

      Gathered download metrics could still be useful to adjust the weights for randomness, so a large server can automatically get more utilized, than a small one.

      p.s. Oh, there are only 220 mirrors now, it seems that 2 have dropped off in just a few days.