🚀 go-pugleaf

In article <kre.732462300@mundamutti.cs.mu.OZ.AU>, kre@cs.mu.oz.au
(Robert Elz) writes:
> In <matth.732433404@extro.ucc.su.OZ.AU>
> matth@extro.ucc.su.OZ.AU (Matthew Hannigan) writes:
> 
> | kre@munnari.OZ.AU (Robert Elz) writes:
> | >What's more, if a file is not actually there in the regular mirrors,
> | >you can always have archie.au fetch it for you, and cache the result so
> | >should anyone else want the same file it doesn't need to be transferred
> | >over the US link again.

> The mechanism is to look in /alex on archie.au - in there you will
> find directories named after top level domains, inside each (most)
> of those you'll find directories named after sub-domains, and so on
> until you find directories named after hosts.  (Caution: some domains

I've just had a brief look at this, and I must congratulate those 
responsible for implementing this system. I just have a few questions and 
comments about it.

Firstly, are there any plans to replace the various mirrors on archie.au 
with (perhaps) links to the original archives? Also, is there any way to 
actively redirect overseas FTP requests to archie's alex filing system? Is 
this not a good idea? I suspect that the caches would work better with more 
traffic, up to a certain limit of course.

The impression I get (note, no figures) is that FTP accounts for the vast 
bulk of traffic on the US link, right? If so, then surely an active 
redirection scheme, if possible, would vastly cut this? Of course, the 
traffic is still really there, but the caching should reduce it 
significantly...

Finally, one "feature" I noticed was that the files I looked at were dated 
1st Jan 1970, what one might call a rather "suspicious" date <grin>.

BTW: All the comments above are on the assumption that the system 
eventually moves out of the testing phase...

Pat -- 668, the neighbour of The Beast...