Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!ginosko!uunet!ficc!peter
From: peter@ficc.uu.net (Peter da Silva)
Newsgroups: comp.mail.uucp
Subject: Re: New UUCP Protocol (was: Re: Zmodem added to UUCP)
Message-ID: <6494@ficc.uu.net>
Date: 10 Oct 89 17:26:48 GMT
References: <3217@ccnysci.UUCP> <240@tabbs.UUCP> <1024@faatcrl.UUCP> <280@atti07.ATT.COM> <9745@chinet.chi.il.us> <754@cybaswan.UUCP>
Reply-To: peter@ficc.uu.net (Peter da Silva)
Organization: Xenix Support, FICC
Lines: 23

In article <754@cybaswan.UUCP> iiitsh@cybaswan.UUCP (Steve Hosgood) writes:
> A single-program-that-handles-everything is an Algol-68 style answer, in other
> words a program so complex that no-one ever gets around to implementing the
> whole thing - only subsets. That's what we've got now with UUCP...

Actually, the UUCP protocol suite is pretty modular. You have a file transfer
program, a queueing program, a batch execution program, and so on. It could
certainly be more modular, yes. But by contrast with other, similar, programs
I've used (UUPC, Fido) it's clean.

Now that I've said that, I do think protocol modules (and dial modules,
and chat modules, etc...) are a good idea.

Among other advantages...

With ANI, and a modem that understands it, it might be possible some day
to make email as convenient as FAX: "mail 7134385018!peter". If you know
the number a caller used, you can feel fairly safe about letting him in.
-- 
Peter da Silva, *NIX support guy @ Ferranti International Controls Corporation.
Biz: peter@ficc.uu.net, +1 713 274 5180. Fun: peter@sugar.hackercorp.com. `-_-'
                                                                           'U`
Quote: Structured Programming is a discipline -- not a straitjacket.