I'm just going to say that such an addition is unnecessary and might just add more headache than is needed. For example, let's assume that such a cron job was to be run on the perlmonks machine(s). It may happen that for some reason, search.cpan.org is unreachable from the perlmonks server but is reachable from where I am. Just because one client can't reach a server doesn't mean that others are unable to connect.
Besides, it's nice to think that node contents are static, unless the author (or in certain cases, janitors or gods) changes the content intentionally. Just my $0.02 CDN.
In reply to Re: Making cpan:// link dynamic?
by saskaqueer
in thread Making cpan:// link dynamic?
by castaway
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |