Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!hplabs!ucbvax!COGSCI.BERKELEY.EDU!bryce
From: bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Note on Interactive task priority implementation
Message-ID: <8706251111.AA08860@cogsci.berkeley.edu>
Date: Thu, 25-Jun-87 07:11:44 EDT
Article-I.D.: cogsci.8706251111.AA08860
Posted: Thu Jun 25 07:11:44 1987
Date-Received: Sat, 27-Jun-87 01:44:51 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 19


> Ideally the system would have a provision for a special task bit
> of "INTERACTIVE".  A interactive task would receive the processor before
> other tasks of the same true priority, *BUT* if for n consecutive slices it
> hogged the processor, the other tasks could get some slices.

My canidate for this bit would be in Intuition's window and screen
structures.  A strange place until you consider that Intuition knows
best about ACTIVE windows, and adding the bit and tacking on a
pointer would be %100 backwards compatible to V1.0, V1.1 & V1.2.

For obvious reasons there is only one active interactive task at a time.

|\ /|  . Ack! (NAK, EOT, SOH)
{O o} . 
( " )	bryce@cogsci.berkeley.EDU -or- ucbvax!cogsci!bryce
  U	I'd like to rotate the guy that invented the BPTR!

This message VOID in states where it is illegal to flame oneself.