cyrus@symplex.UUCP (cyrus) (06/16/85)
> re: *positive* flow control ("I'm OK for another 347 characters now"). > > HP terminals use a similar protocol: ENQ/ACK (although most HP systems seem > to be moving to XON/XOFF, also supported by current HP terminals). The > difference between ETX/ACK and ENQ/ACK is that the ENQ is sent BEFORE the 80 > characters of data, instead of afterwards. Of course, once the stream has > started, there's really no difference. > > Regards, Hewlett-Packard > Bob Niland 3404 East Harmony Road > hplabs!hpfcla!rjn Fort Collins CO 80525 I would like a well informed netter to comment on how various stat muxes implement the HP ENQ/ACK protocol. Many async stat muxes have a special HP option to handle this. Without this special option thruput goes way down due to the varying delay all stat muxes have. I have been told that most stat muxes simply send an ACK back to the host every time they see an ENQ. Unless the HP protocol is very forgiving, it seems to me this could cause great confusion and hurt the proper functioning of the flow control method. Any enlightenment is greatly appreciated.... "So this is the -Cyrus Azar (313) 995-1555 || ihnp4!umich!symplex!cyrus dining room?!" Symplex Communication Corporation "one, two, three, faahh!" 5 Research Drive Ann Arbor, MI 48103