Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site watcgl.UUCP
Path: utzoo!watmath!watcgl!dmmartindale
From: dmmartindale@watcgl.UUCP (Dave Martindale)
Newsgroups: net.dcom
Subject: Re: XON/XOFF as flow control?
Message-ID: <1082@watcgl.UUCP>
Date: Mon, 14-Nov-83 10:47:30 EST
Article-I.D.: watcgl.1082
Posted: Mon Nov 14 10:47:30 1983
Date-Received: Wed, 16-Nov-83 00:41:47 EST
References: <981@utah-gr.UUCP>
Organization: U of Waterloo, Ontario
Lines: 13

Re the DEC-20 "reasonableness check" interacting with Able hardware flow
control:  This is simply an example of the assumptions of your tty driver
(characters are always transmitted continuously) conflicting with the
assumptions of the person who installed your Able boards (hardware flow
control is transparent to the host so let's use it).  The solution is simply
to fix the driver or not use hardware flow control.  This has nothing to
do with the desirableness of XON/XOFF flow control.
In the case of your LocalNet, why not have your terminal do XON/XOFF
handshaking with your localnet box, the network do its own out-of-band
flow control, and the host's localnet interface to XON/XOFF flow control
with the host?  There is no need to do terminal-to-host flow control.
This should eliminate the long delay between sending XOFF and the cessation
of characters being received.