Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!adm!hoey@nrl-aic.arpa
From: hoey@nrl-aic.arpa (Dan Hoey)
Newsgroups: comp.unix.wizards
Subject: Telnet flow control
Message-ID: <8797@brl-adm.ARPA>
Date: Fri, 14-Aug-87 11:26:03 EDT
Article-I.D.: brl-adm.8797
Posted: Fri Aug 14 11:26:03 1987
Date-Received: Sat, 15-Aug-87 18:28:46 EDT
Sender: news@brl-adm.ARPA
Lines: 51


    Date: Tue, 9 Jun 87 07:39:24 EDT
    From: scott@gateway.mitre.ORG
    Message-Id: <8706091139.AA00676@vlsi-a.mitre.org>
    To: unix-wizards@BRL.ARPA
    Subject: Telnet flow control

    ...The problem is that the distributed telnet turns off local flow
    control (UCB telnet that is, I can't speak for other telnets).  Here is
    a modified ``mode'' function taken from a 4.2bsd telnet that reinstates
    local flow control....

		John <scott@gateway.mitre.org>

    ...
		tc = &notc;
		tc->t_stopc = otc.t_stopc;		/* hacks to allow */
		tc->t_startc = otc.t_startc;		/* flow control */
		ltc = &noltc;
    ....

Well, I got the same complaints, but I am *not* willing to forgo the
ability to send ^S/^Q to the remote host.  The easy way to do this was
to also copy the ^V (literal-next) out of the terminal characteristics.
So if you want to send ^S, ^Q, or ^V over the telnet, you precede them
with ^V.

Since this would annoy people people who just want to type ^S and damn
the flow control, I put the whole thing under control of a telnet flag
(-x) and command (xonxoff) that toggles the state.  The relevant
section of the mode routine then looks like

    ...
	    tc = &notc;
	    ltc = &noltc;
	    if (xonxoff) {
		tc -> t_startc = otc.t_startc;
		tc -> t_stopc = otc.t_stopc;
		ltc -> t_lnextc = oltc.t_lnextc;
	    }
	    else
		tc -> t_startc = tc -> t_stopc = ltc -> t_lnextc = -1;

    ....

Maybe when I fit it into 4.3 I'll send the fixes to Berkeley, though
after the CRLF wars I'm not sure they'll want to listen.

Dan Hoey
Internet: HOEY@NRL-AIC.ARPA
UUCP: IICP: WEALLCP: for MCP