Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!sdcsvax!ucbvax!QUABBIN.SCRC.SYMBOLICS.COM!DCP
From: DCP@QUABBIN.SCRC.SYMBOLICS.COM (David C. Plummer)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: RCTE
Message-ID: <870929154835.2.DCP@KOYAANISQATSI.S4CC.Symbolics.COM>
Date: Tue, 29-Sep-87 15:48:00 EDT
Article-I.D.: KOYAANIS.870929154835.2.DCP
Posted: Tue Sep 29 15:48:00 1987
Date-Received: Thu, 1-Oct-87 04:35:43 EDT
References: <PADLIPSKY@A.ISI.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 8

I assumed, incorrectly it turns out, that your requests for local
echoing and display-oriented terminal service were separate.  If your
goal is to minimize network traffic, then indeed, SUPDUP is not for you.
if your goal is to minimize program (e.g., editor) wakeups, then you
can still use SUPDUP as is.  You do need to make a system call that
causes the system, not the program, to do the echoing and return control
to the program on the special characters.  ITS has such a system call.
Multics has such a system call and/or communication with its front end.