Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!cornell!batcomputer!pyramid!ctnews!mitisft!andrew
From: andrew@mitisft.UUCP
Newsgroups: comp.protocols.tcp-ip
Subject: Re: RCTE
Message-ID: <244@mitisft.Convergent.COM>
Date: Tue, 29-Sep-87 18:32:55 EDT
Article-I.D.: mitisft.244
Posted: Tue Sep 29 18:32:55 1987
Date-Received: Fri, 2-Oct-87 00:45:16 EDT
References: <8709281505.AA02244@ucbvax.Berkeley.EDU>
Distribution: world
Organization: Convergent Technologies, San Jose, CA
Lines: 20


	It seems to me there are is a middle ground in here, between
char-at-a-time and line- (or screen-) at-a-time, that can be implemented
purely on the server side using the normal telnet protocol (ECHO negotiation).
We are considering implementing this for support of low speed TCP links
(eg async modems), and I'm curious if I'm going to run into some "common
knowledge problem"...

        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.

	Has anyone tried this?  The UCB virtual terminal driver has some
hooks in it ("packet mode", currently used for flow control negotiation
with rlogin) that could be used for this (after extension).

Andrew Knutsen
(408)435-3623