🚀 go-pugleaf

In article <3138@garth.UUCP> phipps@garth.UUCP (Clay Phipps) writes:
>In article <2968@scolex.sco.COM> seanf@scolex.UUCP (Sean Fagan) writes:
>>In article <164@bms-at.UUCP> stuart@bms-at.UUCP (Stuart Gathman) writes:
>>
>>>Most of the massive I/O bandwidth on mainframes is wasted 
>>>due to stupid software.   They can copy files at 3 Mbytes/sec, 
>>>but even with only one user, editing is faster on a PC. 
>
    
    [...Cyber editors are:  fast  xor  correct...]

  To get decent screen I/O performance out a typical mainframe takes
  some doing (but it obviously can't compete with memory mapped PC
  screens for a single user).

  Our NAS 9160 (an IBM-alike) uses two UVAXIIs as terminal/editing
  front-ends as below (there is also a VS2000 which does the same
  for telnet sessions):


  +------------+         +--------+
  |            | channel |        |
  |  NAS 9160  +=========+ uVAXII +~~~~~~~ fiber to campus backbone
  |            |         |        |          to serial terminal lines
  +------------+         +--------+


  and each uVAX supports 90 terminal seesions (the capacity of the
  fiber link) each doing full-screen editing as fast as you can type. 
  The uVAX takes care of all the cursor stuff and just reads/sends
  lines/pages over the channel as it needs.

John Hascall
(at least this topic is *hopefully* swinging back toward architecture)