Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!killer!ames!ucsd!ucsdhub!hp-sdd!hplabs!hpda!hp-sde!hpfcdc!hpldola!hp-lsd!hpcsla!hpcsrc!bdale
From: bdale@hpcsrc.HP.COM (Bdale Garbee)
Newsgroups: comp.dcom.lans
Subject: Re: Terminal servers over ethernet?
Message-ID: <230002@hpcsrc.HP.COM>
Date: 7 Jul 88 16:50:28 GMT
References: <320@ucrmath.UUCP>
Organization: HP Colorado Springs Division
Lines: 15

>There is work on SLIP support on terminal servers, although BU isn't
>running SLIP yet.  I wonder how many SLIP ports a typical terminal
>server could support?  Is SLIP more compute intensive than telnet?
>
>	Kent England, Boston University

In general, SLIP should be less compute intensive than telnet for a terminal
server, since there are only packet routing decisions to be made, and the
IP frames don't have to get unpacked and processed, etc.  However, SLIP links
tend to have heavier data flow than a Telnet session, so they are likely to
impose more load on a terminal server than a Telnet session.  Overhead per
unit data is typically lower, but there's more data...

Bdale, N3EUA
bdale%hpcsla@hplabs.hp.com