Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!rutgers!ucsd!ucbvax!ATHENA.MIT.EDU!mar From: mar@ATHENA.MIT.EDU Newsgroups: comp.protocols.tcp-ip Subject: telnet... Message-ID: <8807061753.AA07059@TOTO.MIT.EDU> Date: 6 Jul 88 17:53:43 GMT References: <12412000929.19.BILLW@MATHOM.CISCO.COM> Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 14 A "DON'T TELNET ANYMORE" option can save you a whole lot on efficiency. I don't just mean taking a couple of conditionals out of the main loop in a telnet server. For example, on the ITS operating system, the supdup server was only involved in starting up a connection. Once the connection was established, a system call tied the network connection to the pseudo-tty that the command interpreter was on, and the server process was no longer in the loop. If there was a way to make sure that no more telnet options processing would need to be done, a similar thing could be done with telnet on other operating systems, saving 2 process-switches per character. -Mark