Clemens Eisserer wrote:
>> xwindow-discuss (cc'ed) would be a better place to
>> ask, IMO.
> Thanks for CC'ing :)
>
>> AFAIK, it's still the traditional one, but one of the
>> regulars in xwindow-discuss
>> should know for sure.
Yes, we still use Xlib's original backend, not xcb.
> Hmm, does somebody know wether there are plans to switch to the XCB based
> xlib by default?
Yes, but as discussed here last month, there's a lot of work that has to happen
first before we're ready, due to things we need to handle in Solaris Xlib that
don't affect Linux distros. (Some because of platform differences, some
because of Solaris changes we haven't upstreamed yet.)
Right now, we're concentrating on the Xorg server 1.5.x migration first,
and finishing up the conversion of our old X11R6-forked/partially-encumbered
sources to the current X11R7/open-source releases, so that we can then more
easily deal with things like XCB integration.
> That rewrite had quite a long time to mature on Linux, and the "traditional"
> Xlib isn't worked on very activly.
While I am a fan of xcb, I wouldn't hold up it's maturity quite yet - the
reworking of the Xlib<->xcb interactions to avoid deadlocks in applications
like the Java Runtime with certain bugs in locking between threads is only
a few weeks old, and while promising, a bit soon to call "mature".
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
