🚀 go-pugleaf

In article <EMV.91May18124540@poe.aa.ox.com> emv@ox.com (Ed Vielmetti) writes:
> > hypothetical rftp program
> The spec should cover at least the following:
> - format of remote files (e.g. sprite.berkeley.edu:/mx.tar.Z)

It would have to be in native remote-system format. If that's not UNIX format
a local file name would have to be provided. Wildcards could be used for
systems that support "mget".

It may be that there is sufficient variation in FTP systems that this would
require the user to provide an FTP script.

uux - uunet!rftp ~/from-uunet
OPEN sprite.berkeley.edu
CD ~ftp
GET mx.tar.Z mx.tar.Z
QUIT

> - specification of alternate delivery mechanisms, e.g. uuencoded and
>   mailed, queued at some grade for delivery, immediate call-back, left
>   in a spool to be picked up later.

So long as the host running the service can disable any of these.

The "mirroring" and archie-search stuff implies a fair amount of smarts from
this server. I would hope a dumb server would be made available when you know
you're getting something not part of an official archive (alpha software, for
example). That sort of thing is where normal archive access really falls down.

But don't let this stand in the way of your more aggressive project.
-- 
Peter da Silva; Ferranti International Controls Corporation; +1 713 274 5180;
Sugar Land, TX  77487-5012;         `-_-' "Have you hugged your wolf, today?"