Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!mimsy!oddjob!hao!noao!arizona!amethyst!rsm From: rsm@amethyst.UUCP (Robert Maier) Newsgroups: comp.protocols.tcp-ip Subject: Re: SUPDUP Message-ID: <273@amethyst.UUCP> Date: Wed, 31-Dec-69 18:59:59 EDT Article-I.D.: amethyst.273 Posted: Wed Dec 31 18:59:59 1969 Date-Received: Sat, 10-Oct-87 19:25:14 EDT References: <8709261909.AA10409@topaz.rutgers.edu> <870928095131.6.DCP@KOYAANISQATSI.S4CC.Symbolics.COM> Reply-To: rsm@amethyst.ma.arizona.edu (Robert Maier) Organization: Dept. of Math., Univ. of Arizona Lines: 23 In article <870928095131.6.DCP@KOYAANISQATSI.S4CC.Symbolics.COM> David C. Plummer writes: >There is and has been a display oriented terminal protocol for a >long, long time. ... I'm referring, of course, to the SUPDUP >protocol, RFC 734 of 1978. If you want graphics, you can do that >too: the SUPDUP Graphics extension, RFC 746 March 1978. It's my impression that SUPDUP (as described in Richard Stallman's 1983 AI Lab Memo 644; I don't have the RFC's handy) doesn't support alteration of display terminal characteristics after the connection initialization takes place. Wouldn't that rule out its use in a modern windowing environment? Windows can be resized. It looks like a very nice job, just the same. I have a generic Unix implementation here; are there any implementations of the graphics extension available for SunView or X Windows? @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Robert S. Maier | Internet: rsm@amethyst.ma.arizona.edu Dept. of Math. | UUCP: ..{allegra,cmcl2,hao!noao}!arizona!amethyst!rsm Univ. of Arizona | Bitnet: maier@arizrvax Tucson, AZ 85721 | Phone: +1 602 621 6893 / +1 602 621 2617