Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!edsews!uunet!van-bc!sl
From: sl@van-bc.UUCP (pri=-10 Stuart Lynne)
Newsgroups: comp.mail.uucp
Subject: Re: Hardwired "g" protocol values
Message-ID: <2268@van-bc.UUCP>
Date: 5 Mar 89 19:16:26 GMT
References: <60827@pyramid.pyramid.com> <455@lakart.UUCP> <61288@pyramid.pyramid.com>
Reply-To: sl@van-bc.UUCP (pri=-10 Stuart Lynne)
Organization: Wimsey Associates, Vancouver, BC.
Lines: 18

In article <61288@pyramid.pyramid.com> csg@pyramid.pyramid.com (Carl S. Gutekunst) writes:
>Note that reverse-engineering the 'g' protocol is *damn* hard. Few have done
>so without making grave sacrifices; UUPC and uuslave, for example, came out
>supporting only a window size of 1, and gave up under almost any error con-

uupc supports a window size of 7.

>dition that the AT&T 'g' implementation would plow right through. Indeed, the
>'g' protocol is by far the biggest stumbling block to producing a PD UUCP.

The g protocol stuff in uupc is quite sound. Adding some additional error
recovery wouldn't be too hard. 

uupc's main problems lie with lack of documentation and a horrible user
interface. 

-- 
Stuart.Lynne@wimsey.bc.ca {ubc-cs,uunet}!van-bc!sl     Vancouver,BC,604-937-7532