Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.org.usenix Subject: SLIP or PPP instead of G proto (Re: USENIX Board Studies UUCP) Keywords: file-transfer protocol modem Message-ID: <7228@ficc.uu.net> Date: 7 Dec 89 18:43:45 GMT References: <320@cfcl.UUCP> Reply-To: peter@ficc.uu.net (Peter da Silva) Organization: Xenix Support, FICC Lines: 21 One thing that people seem to miss in the discussion of whether SLIP or PPP is appropriate for uucp++ is that the current connect-time efficient batch protocol can be maintained, with a uucp spool directory and so on, under IP. You just queue up the requests, and when time comes to poll you dial-up, go into IP, and transfer files in both directions as fast as you can. Then you hang up and run uuxqt. This wouldn't even need to allow interactive use of the link. Phil Karn's KA9Q would do just fine, without even dealing with real sockets. But you could also *add* sockets later and start interacting with that big old hub when you got better software. The problem is how you set up something like dial-up IP started under a hypothetical modular UUCP. Any ideas? At least design your uucp++ so that full-duplex protocols like IP can co-exist with it. -- `-_-' Peter da Silva. +1 713 274 5180. . 'U` Also or . "If you want PL/I, you know where to find it." -- Dennis