Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!shelby!Portia!hanauma!rick
From: rick@hanauma (Richard Ottolini)
Newsgroups: comp.windows.x
Subject: Re: XPutImage limit
Message-ID: <2428@Portia.Stanford.EDU>
Date: 22 May 89 08:31:25 GMT
Sender: USENET News System <news@Portia.stanford.edu>
Reply-To: rick@hanauma (Richard Ottolini)
Organization: Stanford University, Dept. of Geophysics
Lines: 8


XputPutImage is one of the few Xlib calls with potentially a huge argument.
There are three places for bottlenecks:
(1) TC/IP chopping.  For example, our Convex computer will only ship 8K bytes
at a time and mess up internet XPutImage commands.
(2) Socket limits. Xlib arguments pass through UNIX sockets in most implementations.
(3) XPutImage chopping.  I notice the DEC-3100 and SONY servers split an image
into 64K chunks, but the Sun server does not.