Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!decvax!ucbvax!MATHOM.CISCO.COM!BILLW
From: BILLW@MATHOM.CISCO.COM (William Westfield)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: RCTE
Message-ID: <12338789015.10.BILLW@MATHOM.CISCO.COM>
Date: Wed, 30-Sep-87 13:52:24 EDT
Article-I.D.: MATHOM.12338789015.10.BILLW
Posted: Wed Sep 30 13:52:24 1987
Date-Received: Sun, 4-Oct-87 22:43:36 EDT
References: <244@mitisft.Convergent.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20


    The basic idea is to have the kernel (virtual terminal driver) inform
    the telnet daemon when it *would be* doing immediate character echo,
    and not do it.  The daemon turns this information into echo
    negotiation, which the client (hopefully) heeds.  This results in
    speeded echo response in (for example) un*x "cooked" mode, plus a
    reduction in packet traffic.

This means that the client must send every character immediately to
the host, and then wait (for an indeterminate time) for a response
from the host that indicates whether the next characters should not
be echoed.  (This is in the worst case, of course.  If you are willing
to assume that when the client is doing local echo, it is doing local
echo of ALL characters, and that it doesn't matter if the client
accidently echos some characters it should not have or doesn't echo
some characters it should have, it may indeed help...)

Bill Westfield
cisco Systems
-------