Hi, One consideration to keep in mind here is that the X server's protocol and requests are carefully designed to work over a socket. For example, avoiding round trips (round trip = sending a request, then blocking for a reply, such as a return value or error code).
If you export an in-process API like Clutter "as is" over a socket, then it will not be designed in that way, and will likely be prohibitively inefficient for nontrivial uses. If you want to make an API look the same either over the network or locally, the way to do this is to make the API look like a network API. It does not work to have something that looks like a local API but is really over a socket. In short I think you'd have to carefully design a remote API for controlling clutter, and should not expect this remote API to look like the current Clutter headers or to be possible to automatically generate. Havoc -- To unsubscribe send a mail to [EMAIL PROTECTED]
