Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site decvax.UUCP
Path: utzoo!linus!decvax!minow
From: minow@decvax.UUCP (Martin Minow)
Newsgroups: net.unix
Subject: Re: rts/cts - a tutorial on flow control
Message-ID: <79@decvax.UUCP>
Date: Sat, 25-May-85 12:43:44 EDT
Article-I.D.: decvax.79
Posted: Sat May 25 12:43:44 1985
Date-Received: Sun, 26-May-85 21:38:40 EDT
References: <5620@utzoo.UUCP>
Lines: 19

... "What is really wanted is a standard method of *positive* flow
control.  I.e., 'I'm ready for another 347 bytes now'."

The "negative" flow-control methods work (XOFF/XON) work satisfactorily
if sufficient space is allocated for overrun.  For example, (assuming
9600 Baud transmission) the receiver can allocate a 400 byte buffer, sending
XOFF when there are 100 bytes unprocessed bytes in the terminal input
buffer.  This gives the host about 600 msec. to stop output.
The terminal might send XON when, say, only 50 bytes are in the input
buffer.  (Actual numbers are made up and shouldn't be taken as
a recommendation -- a university-level course on simulation might
give you tools for selecting real values.)

As has been already noted, it is important to implement flow-control
algorithms at a low-level in the operating system, preferably within
the terminal device interrupt-service routine.

Martin Minow
decvax!minow