Xref: utzoo comp.mail.misc:5470 comp.mail.uucp:6541
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!ncar!midway!clout!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.mail.misc,comp.mail.uucp
Subject: Re: BITFTP grief!
Message-ID: <1991May18.175515.4071@chinet.chi.il.us>
Date: 18 May 91 17:55:15 GMT
References: <1991May16.145758.6817@uu.psi.com> <MDDB7-A@xds13.ferranti.com> <1991May17.202220.9531@uu.psi.com>
Distribution: na
Organization: Chinet - Chicago Public Access UNIX
Lines: 33

In article <1991May17.202220.9531@uu.psi.com> schoff@uu.psi.com (Martin Schoffstall) writes:

>>"uux uupsi!rftp sprite.berkeley.edu:~ftp/mx.tar.Z (ficc!~/from-uupsi)"

>But lets go back to your rftp, what you need to do is create the
>code and make it work across 2 dozen platforms and it will be
>as explosive as CNews use.  So get the community to work the
>spec and write the code and we're off, minimum portability would be

Build it into a kermit server and it will work on many dozens of
platforms that already exist and you can make it interactive
for doing directories down mutliple levels, etc.  Just make
REMOTE DIR understand host:dir, and GET should understand host:file. 

>bsd4.x
>sunos
>sysv
>xenix
>ice's Uaccess
>uupc
>aix
>Your biggest and most controversial design decision will be to
>decide if this works one hop or multiple hops.

Making a mail server that runs on your machines would handle all of
this, since these users obviously already have mail access.  Just
make the server check a list of allowable paths before sending it
down multiple hops.  If they are your subscribers you should be
able to get this information easily.  No changes to anything else
would be necessary. 

Les Mikesell
  les@chinet.chi.il.us