[Xcb] icccm

Vincent Torri Vincent.Torri at iecn.u-nancy.fr
Sun Mar 20 14:12:39 PST 2005

On Sun, 20 Mar 2005, Jamey Sharp wrote:

> On Sun, Mar 20, 2005 at 04:01:06PM -0500, Kevin Brosius wrote:
> > Yes.  This is the general direction we're headed with evas and ecore, I
> > think.  These two libs are the core xlib using libraries for new
> > enlightenment development.  Evas focuses on drawing and canvas
> > operations, while ecore leans toward the window creation, management,
> > communications, etc (that's really a broad swipe.)  It's great to see
> > the evas progress Vincent!
> Thanks for the explanation. What's a canvas library doing with ICCCM
> though?

the use of icccm is just in a test program.

> > We've had a couple short discussions about architecture and you point
> > out the major benefit of XCB we hope to get to, Jamey.  If responses can
> > be tied to an expected response queue (I'm guessing), then Sync's can be
> > largely avoided, or at least not block in all cases.  We'll have to see
> > how it goes. :)
> Sure, you can queue the reply cookies that XCB gives you. If you can be
> certain that you enqueue them in the order that XCB produces them, then
> they'll be in the same order as the returning replies, so you can
> minimize latency there. That's an easy invariant to maintain as long as
> you have one queue per thread (which is obviously true if you're
> single-threaded).
> I look forward to hearing how this goes!

i'm a bit lost with all this queue stuff. But once the code will be in
cvs, it'll be easier to modify it


More information about the xcb mailing list