[Xcb] problem when getting replies

[Vincent Torri]

On Sun, 12 Nov 2006, Jamey Sharp wrote:

>
>> How do I use xcb_get_maximum_request_length ? I just store its value
>> somewhere and I don't use it ? Or should I use it somewhere ?
>
> You don't have to store the return value. (More reason to have a
> 'prefetch' variant that has no return value...) XCB caches the maximum
> request length, so after the first time, calling it is fast.
>
> You should use it when constructing a request that might get big,
> though. If you construct a request that's too big, XCB will detect that
> it can't send it, and shut down your connection.
>
> Now, exactly how to use it for this purpose isn't entirely obvious. It's
> an area that needs a bit of thought still.

what kind of request might get big ?

> Could you test across an internet connection? You know, `ssh -X`
> somewhere and run the benchmarks on the remote machine? I bet you'd get
> even more dramatic numbers, especially over a link with >100ms round
> trip time.

here are a bench:

ecore_x time...: 6.475370
ecore_xcb time.: 1.112529

>
>> I don't know if that is important for the numbers, but I run a non
>> optimized XCB (compiled with -g).
>
> It shouldn't have much effect here: these measurements should be
> dominated by round-trip delay.

ok

Once in cvs, can someone (you ?) review ecore_xcb a bit ?

Vincent