Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!labrea!decwrl!jumbo!jg
From: jg@jumbo.dec.com (Jim Gettys)
Newsgroups: comp.windows.x
Subject: Re: XNextEvent/XPending bug in v10?
Message-ID: <910@jumbo.dec.com>
Date: Sat, 29-Aug-87 20:20:15 EDT
Article-I.D.: jumbo.910
Posted: Sat Aug 29 20:20:15 1987
Date-Received: Sun, 30-Aug-87 10:11:01 EDT
References: <1915@tekcrl.TEK.COM>
Reply-To: jg@jumbo.UUCP (Jim Gettys)
Organization: DEC Systems Research Center, Palo Alto
Lines: 14

Yeah, the routines should probably read as much as possible.  It still
would not prevent deadlock, but make it less likely.

In V11, the problem is solved in a better way, requiring more sweeping
changes.  The connection is run in non-blocking mode, and if you would block
writing data to the server, events are enqueued in the meanwhile by
reading events from the connection until all data has successfully
been written.  This still does not entirely prevent problems, as a 
completely antisocial client may not ever do anything with his connection 
and the server still has to give up sending him data eventually.  

Then again, dealing with catatonia is hard under any circumstances....
				Jim Gettys
				Digital Equipment Corporation.