RFC: server-side XCB

[Jamey Sharp]

We've talked about doing the xserver equivalent of XCB for years--that is,
auto-generating the protocol serialization and deserialization code from
XCB's machine-readable descriptions of the X protocol and extensions.

Considering the recent CVEs in that code, I think it's time. So I want to
collect folks' thoughts on what server-side XCB should look like.

At a high level, which code should we be generating? Off the top of my
head, I'm thinking the dispatch tables and all the swap procedures, as a
first target in order to get the codegen infrastructure merged and tested.
Then it'd be nice to generate code that validates arguments and returns
appropriate errors. Thoughts?

XCB's code generator is implemented in Python. Can we make the same choice
in the xserver build process?

Anything else I should be thinking about?
Jamey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-devel/attachments/20141220/587296ca/attachment.html>