Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!dimacs.rutgers.edu!seismo!uunet!ora!bloom-beacon!dont-send-mail-to-path-lines
From: doug@genmri.UUCP (Doug Becker)
Newsgroups: comp.windows.x
Subject: XMaxRequestSize, and Xlib
Message-ID: <9101311815.AA14578@genmri.sane.COM>
Date: 31 Jan 91 18:15:44 GMT
References: <9101301952.AA29228@excess.lcs.mit.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 18

While we're on the subject of XMaxRequestSize, I've noticed that there is
no definitive documentation describing when the client must break up poly
requests and when Xlib will do it automatically.  For example, the MIT
implementation automatically chops up XDrawPoints calls, but doesn't chop
up XDrawLines calls.  This makes sense empirically since chopping up the
latter request could possibly disturb the server's joining of lines.

I understand that few vendors provide their own Xlib implementations, but
it would be nonetheless beneficial if the distinction between Xlib
poly-request-generating routines that chop up requests and those that do
not were part of the Xlib standard.  (Until then, I guess I'll just have to
chop up all poly requests suitably myself, in the client.)

-- 

Doug Becker
doug@nmri.ge.com
crdgw1.ge.com!sane!doug