Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!uw-beaver!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.UUCP
Newsgroups: comp.sources.d,comp.terminals
Subject: Re: VT100's keeping up at high baud rates
Message-ID: <13758@teknowledge-vaxc.ARPA>
Date: Wed, 17-Jun-87 01:30:45 EDT
Article-I.D.: teknowle.13758
Posted: Wed Jun 17 01:30:45 1987
Date-Received: Fri, 19-Jun-87 00:46:32 EDT
References: <1149@carthage.swatsun.UUCP> <8601@tekecs.TEK.COM>
Reply-To: mkhaw@teknowledge-vaxc.UUCP (Michael Khaw)
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 17
Xref: utgpu comp.sources.d:795 comp.terminals:285

In article <1490@ho95e.ATT.COM> wcs@ho95e.UUCP (46133-Bill.Stewart,2G218,x0705,) writes:
>have a terminal that can keep up with 19200 without flow control (i.e. 
>continuous text display), that's approximately 19200 words per minute, and
>neither you nor I nor Evelyn Wood's mother can read that fast over sustained
>periods.  The reasons you'd want a terminal to go that fast without flow

Actually, a lot of the time I don't want to read everything that's coming up
on the screen.  What I really care is that things like screen refresh ought
not to keep me waiting.  19200 bps is 1920 chars/sec, which is one 24x80 screen
in 1 second (admittedly worst case).  I consider that speed barely adequate.
Twice that speed would come close to being tolerable.

Mike Khaw
-- 
internet:  mkhaw@teknowledge-vaxc.arpa
usenet:	   {hplabs|sun|ucbvax|decwrl|sri-unix}!mkhaw%teknowledge-vaxc.arpa
USnail:	   Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303