Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ucbvax!ucbcad!nike!rutgers!im4u!ut-sally!std-unix
From: std-unix@ut-sally.UUCP (Moderator, John Quarterman)
Newsgroups: mod.std.unix
Subject: multiplexing vs windows
Message-ID: <5986@ut-sally.UUCP>
Date: Sat, 11-Oct-86 02:23:59 EDT
Article-I.D.: ut-sally.5986
Posted: Sat Oct 11 02:23:59 1986
Date-Received: Sat, 11-Oct-86 11:18:28 EDT
References: <5932@ut-sally.UUCP>
Organization: IEEE P1003 Portable Operating System for Computer Environments Committee
Lines: 28
Approved: jsq@sally.utexas.edu

From: pyramid!utzoo!henry
Date: Fri, 10 Oct 86 20:38:59 CDT

The following was sent to me in private mail, with permission to publish.
He's got an interesting point.

				Henry Spencer @ U of Toronto Zoology
				{allegra,ihnp4,decvax,pyramid}!utzoo!henry
-----
>From: ihnp4!mecc!sewilco
Subject: Re: Window-based multiplexing

My opinion is that the multiplexing characteristic of a line should be
separated from the windowing.  The multiplexing should also not be
terminal-oriented so it can be used as a multiplexed intersystem line.

I've heard several people echo my wish to be able to have file transfer
multiplexed with a terminal session, or have high-priority transfers
be interleaved with a long low-priority transfer.  And with computer
ports always in short supply it would be nice to use a $600 multiplexer
to add a few more terminals and printers (several WY-50 on a table is a
poor man's windowing system).

Scot E. Wilcoxon    Minn Ed Comp Corp  {quest,dicome,meccts}!mecc!sewilco
45 03 N  93 08 W (612)481-3507                  ihnp4!meccts!mecc!sewilco
-----

Volume-Number: Volume 7, Number 48