Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!udel!gatech!mcnc!decvax!ima!cfisun!lakart!dg
From: dg@lakart.UUCP (David Goodenough)
Newsgroups: comp.mail.uucp
Subject: Re: New UUCP Protocol (was: Re: Zmodem added to UUCP)
Message-ID: <710@lakart.UUCP>
Date: 2 Oct 89 14:34:43 GMT
References: <1024@faatcrl.UUCP>
Organization: Lakart Corporation, Newton, MA
Lines: 37

jimb@faatcrl.UUCP (Jim Burwell) sez:
> aris@tabbs.UUCP (Aris Stathakis) writes:
>>The 'g' protocol is a bit outdated.  We need something NEW and better.
>>Some ideas i had -
> 
> The 'g' protocol is a bit outdated.  But it's not as bad as one might think.
> There is a bit of windowing involved, which makes 'g' much faster than 
> other protocols which also require handshakes after every block

Now, let's see. 2400 BPS * 64 data characters per block / 70 actual characters
means you can crank along at about 219 CPS, or 91.4 % of available
bandwith. A good Ymodem / Xmodem 1K can get up to the same neck of the woods:
I usually hit about 214 - 216 CPS on an Xmodem 1K transfer.

What _WOULD_ be worth doing, and uucico has the ability, is to increase the
packet size above that #@%*! 64 byte limit. 256 byte packets would mean 262
actual:

2400 * 256 / 262 == 234 CPS or 97.7 % used bandwidth.

Then if you go to 1024 byte packets ......
2400 * 1024 / 1030 == 238 CPS,
or (all together now :-) ) "ninety nine and fourty four one hundredths
per cent pure data" (actually it's 99.42 %, but what's 2 parts in 10,000
between friends)

Also the g protocol has the ability to run bidirectionally, what is needed is
to adjust the _FILE_ level section to take advantage of this. Maybe, just
maybe, one day I'll do this. Of course, you wouldn't want to do this with a
pair of TB's running PEP - it'd get really messy :-) Or would it - with the
PEP running a packet size the same as the g protocol packet size, it might
just work, although it wouldn't gain you anything. ..... Oh well .....
-- 
	dg@lakart.UUCP - David Goodenough		+---+
						IHS	| +-+-+
	....... !harvard!xait!lakart!dg			+-+-+ |
AKA:	dg%lakart.uucp@xait.xerox.com			  +---+