Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Amiga Keyboard Buffer
Message-ID: <49382@sun.uucp>
Date: 13 Apr 88 17:06:11 GMT
References: <3138@gryphon.CTS.COM> <2021@amiga.UUCP> <1815@sugar.UUCP> <1375@hubcap.UUCP> <1376@hubcap.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 23

Rich, and others, as several people have pointed out there are many buffers
in the Amiga, some of which are not very easy to get to, if you look at
Kodiak's drawing of the input food chain you will note that messages are
buffered from the input.device into the top (or bottom) of the food
chain, make their way through possibly several handlers, each of which
is capable of buffering them, and into the Intuition() zone where they
get *exploded* into a zillion little streams heading out to various 
tasks, one of which being the console.device, which apparently buffers
them as well. One problem with all this, is that there isn't a "back
channel" on the input.device that lets you feed back requests like
"flush everything", or something like the TCP concept of "urgent"
data that gets propogated through the chain at a high priority. Neither
concept is difficult to imagine, although both probably have major 
consequences on the architecture of the input food chain. 

So the answer is, "No, there is no supported way to flush all of the key
board events out of the input food chain." You could always submit it as
a request for enhancement to cbmvax!bugs though. 


--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.