Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: XCreateImage & XPutImage Optimization
Message-ID: <9007241231.AA03157@expire.lcs.mit.edu>
Date: 24 Jul 90 12:31:16 GMT
References: <1990Jul24.030503.4818@eplrx7.uucp>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 19


    I suspect creating the image data in the bit-order
    and byte-order of the server is most efficient,

You are correct.

    but I developed doubts when
    I looked at XImUtils.c and noticed the code normalizes all data to
    LSB byte-order and bit-order.

Um, the functions in that file are not used for XPutImage (at least, not
in the normal case).  You asked specifically about XPutImage.

    Also are other parameters 
    crucial in minimizing server overhead.  For example, are 32 bit scanline 
    pads more efficient than 8 bit?

The scanline pad and bits per pixel should also be chosen to match what
the server wants.