Path: utzoo!utgpu!attcan!uunet!husc6!bloom-beacon!gatech!ncar!oddjob!gargoyle!att!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.dcom.modems
Subject: Re: TrailBlazer and UUCP
Message-ID: <6184@chinet.chi.il.us>
Date: 3 Aug 88 19:48:35 GMT
References: <12793@mimsy.UUCP>
Reply-To: les@chinet.chi.il.us (Leslie Mikesell)
Organization: Chinet - Public Access Unix
Lines: 28

In article <12793@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
>The g-protocol spoofing is neat, but here is a thought:  Would it be
>worthwhile to write an `h' protocol, specifically designed for
>half-duplex high-speed not-necessarily-error-free modems?

YES! But to make it really worthwhile, uucico would need to be changed
to batch the files.

>	- large packets (perhaps 4KB);
>	- a window of at least 256 packets;
>	- checksums per packet, but
>	- ACKs not required except at EOF or window edge

When sending small mail messages or the X.* files from uux, the file
boundaries will be smaller than the window boundaries.  Requiring an
ACK at EOF (and one at the start) will defeat much of the gain if
line turn-around is slow.  The file handling should be windowed to
match the packet window - that is, do not require any ACKs except at
the window edge or at the end of the connection, when all files must
be ACKed.

>	- with NAKs accepted anytime;
>	- characters ^Q and ^S reserved to the modem,
>	  with an escape encoding in the data stream

Why would anyone do it any other way?

  Les Mikesell