Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!mit-eddie!uw-beaver!teknowledge-vaxc!sri-unix!sri-spam!ames!ucbcad!ucbvax!decvax!decwrl!sun!imagen!auspyr!sci!kenm
From: kenm@sci.UUCP
Newsgroups: comp.windows.x
Subject: input queue overflow
Message-ID: <3645@sci.UUCP>
Date: Sun, 5-Apr-87 02:09:05 EST
Article-I.D.: sci.3645
Posted: Sun Apr  5 02:09:05 1987
Date-Received: Wed, 8-Apr-87 04:51:58 EST
Organization: Silicon Compilers Inc., San Jose, Calif.
Lines: 17

I have a problem with the X server thinking my program has died
just because it has temporarily become compute intensive and
stops processing input events.  It reacts by disconnecting.
Is there some way I can configure things so that any events
after the first 16 or so without response by the client are
redirected to the bit bucket?  If this fails, is there some
way I can asynchronously disable input events without flushing
the output queue.  I have tried this with a timer interrupt
but everything that plays with the input queue flushes the
output queue with disasterous consequences if the program
was in the middle of XLine or somesuch.  I can't tell when
the program is going to become compute intensive because it
might just be a heavy load.

Thanks
Ken McElvain
decwrl!sci!kenm