Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!decvax!dartvax!richb
From: richb@dartvax.UUCP (Richard E. Brown)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: supdup protocol and local editing
Message-ID: <7415@dartvax.UUCP>
Date: Mon, 19-Oct-87 10:18:28 EDT
Article-I.D.: dartvax.7415
Posted: Mon Oct 19 10:18:28 1987
Date-Received: Wed, 21-Oct-87 06:26:35 EDT
References: <8710121554.AA07611@armagnac.DEC.COM> <8710140650.AA03966@ucbvax.Berkeley.EDU>
Reply-To: richb@dartvax.UUCP (Richard E. Brown)
Organization: Dartmouth College, Hanover, NH
Lines: 21
Keywords: screen editing back end editor

At Dartmouth, we have been using just such a front/back end
editing scheme for 5 years.  The initial implementation was a
Z-80 box with 32K RAM and 24K ROM which acted as a screen manager
for a simple terminal and talked to a back-end editor on a host.
This setup did two things:  a) it provided "scrollback" of the last n
lines of your session (limited by the 32K RAM), and b) cached a
copy of the hosts file, to provide local editing.  Editing
changes were shipped back to the host, line-by-line.  We had
several hundred around campus, with good results.

We now have a Macintosh version which uses the same back end
editor (now implemented on Unix, VAX/VMS, and DCTS, with VM/CMS
to come).  The Mac provides much more scrollback, and places the
screen editing text in a separate window.  It uses the standard
Macintosh cut-copy-paste paradigms.

Rich Brown                           Telephone:   603/646-3648
Manager of Special Projects          E-Mail: richard.e.brown@dartmouth.edu
Dartmouth College                            richard.e.brown@dartcms1.bitnet
Kiewit Computer Center                       richard.e.brown@dartvax.uucp
Hanover, NH 03755                    AppleLink:  A0183