Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!root
From: root@LARRY.MCRCIM.MCGILL.EDU (el Root)
Newsgroups: comp.windows.x
Subject: Re:  What to emulate?  SUPDUP of course.
Message-ID: <8911181226.AA15934@Larry.McRCIM.McGill.EDU>
Date: 18 Nov 89 12:26:53 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 22

> The discussion about whether to emulate something that exists or to
> invent your own has come around to the reason the SUPDUP protocol was
> first invented.

Supdup is a network protocol, not a choice of terminal to emulate.
It's up to the supdup server what sort of virtual terminal to provide
to programs running on the remote end of a supdup session.  And the
choice of that emulation is what we're discussing here, albeit in a
slightly different context.

Unless I missed something in my pass through RFC734....

In the meantime, I'll just note that if the remote system doesn't
support the terminal type I'm emulating, I'll bring across my own
termcap file and use it.  If the remote system doesn't support supdup
connections, as far as I can see you're SOL, unless you're fortunate
enough to be able to install new network servers there.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu