Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.PCS 1/10/84; site mtuxo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!hfavr
From: hfavr@mtuxo.UUCP (a.reed)
Newsgroups: net.unix-wizards,net.cog-eng
Subject: Re: UNIX Futures
Message-ID: <1483@mtuxo.UUCP>
Date: Thu, 10-Apr-86 13:41:24 EST
Article-I.D.: mtuxo.1483
Posted: Thu Apr 10 13:41:24 1986
Date-Received: Sat, 12-Apr-86 02:41:59 EST
References: <67@cstvax.UUCP> <2864@amdahl.UUCP> <137@myab.UUCP> <6534@utzoo.UUCP> <1524@wucs.UUCP> <1090@psivax.UUCP>
Organization: AT&T Information Systems Labs, Holmdel NJ
Lines: 17
Xref: watmath net.unix-wizards:17536 net.cog-eng:655

Sarima (Stanley Friesen) writes:
> 	Actually, a properly implemented windowing system should
> SIGSTP all processes not in active windows.

I don't think that anyone who has used the asynchronous layering
capability of AT&T windowing (5620,7300 etc) will agree with you.
I want the process in the "deselected" layer - for example, a make
which is running in one window while I am editing other code in another
layer - to keep on writing so I can monitor it. This is the main reason
why windowing increases productivity: so you don't have to stop your
work just because you have to monitor the slow progress of some other
process in real time. The cleanest conceptual model is that layers are
just like separate terminals (in fact, I used to work with two
terminals and a T-switched keyboard before I got a Blit). Are you going
to claim that a process should behave differently depending on whether
the user's keyboard is connected to its terminal?
					Adam Reed (ihnp4!npois!adam)