server-side xcb

[Peter Harris]

On 2010-06-17 20:56, Tomas Carnecky wrote:
> The current code only works with requests/replies which use simple
> fields. Lists etc are not supported yet. One issue is how to represent
> (and swap) dynamically sized fields in the request/reply structures,
> another is how to give the client the ability to write additional data
> after the reply (as in GetImage for example). I'll take a look at how
> xcb solved these problems.

LibXCB solved some of those problems by being on the client side, so it
doesn't swap. (GetImage and PutImage are poor examples for swapping
dynamic lists, since the server defines the byte order of the contents -
no swap is ever performed on the list by the sample implementation.)

Most requests are fully defined by libXCB, but a few (GetProperty and
ChangeProperty spring to mind -- <list type="void">) are a little fuzzy
around the edges.

The current GSOC project adding support for XKB will add support for the
<switch> statement. I suspect that once that is in place, we can use it
for GetProperty and ChangeProperty to get the swapping right.

Peter Harris
-- 
               Open Text Connectivity Solutions Group
Peter Harris                    http://connectivity.opentext.com/
Research and Development        Phone: +1 905 762 6001
pharris at opentext.com            Toll Free: 1 877 359 4866