X display locking

[Alan Coopersmith]

On 03/12/13 12:21 PM, Aaron Plattner wrote:
> On 03/12/2013 11:52 AM, Torsten Jager wrote:
>>> Applications should never call those functions - they are Xlib's
>>> internal locking mechanism for the request buffers.
>>
>>> Applications should only call XInitThreads() to set up the locks
>>> before any Xlib calls are made.
> 
> I think Allen must have been thinking of the Xlib internal LockDisplay and
> UnlockDisplay functions.  However, those functions aren't necessary unless you
> need multiple requests from one thread to be atomic w.r.t. other threads using
> the same display connection.  For your use case, it sounds like you don't need
> them.

Sorry, you're right, I've been looking inside Xlib code too much lately and
read the question as being the internal LockDisplay API, not the external
XLockDisplay API.   Xlib rots the brain you know...

-- 
	-Alan Coopersmith-              alan.coopersmith at oracle.com
	 Oracle Solaris Engineering - http://blogs.oracle.com/alanc