Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!decwrl!bacchus.pa.dec.com!shlump.nac.dec.com!ryn.esg.dec.com!vino.enet.dec.com!withrow
From: withrow@vino.enet.dec.com (Robert Withrow)
Newsgroups: comp.windows.x
Subject: Re: Why is plaid so cpu-intensive?
Message-ID: <1990Oct29.171139@vino.enet.dec.com>
Date: 29 Oct 90 22:12:04 GMT
References: <7208.27287099@swift.cs.tcd.ie> <1990Oct24.225856.6840@elroy.jpl.nasa.gov>
Sender: guest@ryn.esg.dec.com
Reply-To: witr@spooky.uucp (Robert Withrow)
Distribution: na
Organization: R.W. Withrow Associates
Lines: 10

>>Plaid issues the XDrawrectangles() requests but doesn't do a sync() to
>>wait until the rectangles are drawn. Hence the queue of requests to be
>>handled by the X server gets filled up mostly with requests to draw
>>rectangles. 

Which, incidentally, is what makes plaid so usefull for testing server
implementations:  It reallys test the flow control of your transport, and
how you deal with timesharing access between clients.

(Even if it is anti-social)