David Dawes is maybe the most active XFree86 developer and he is also the lead founder of the project. He works for Tungsten Graphics, which is the main company working on the XFree, DRI and Mesa codebases today. We are happy to host an interview with David, discussing the present and future of XFree86 project. Update: Still confused how a VSYNCed desktop look like? Read here.
Permalink for comment
To read all comments associated with this story, please click here.
"""The only other choice is SysV message queues, which are connectionless and therefore difficult to use for the purposes of a display server."""
Have you tried Local Domain sockets? Or perhaps implementing a stateful protocol over the connectionless IPC?
"""Multiplexing multiple connections basically comes down to using one queue, which may lead to some issues such as any application connected to the server being able to "spoof" messages as coming from a different application."""
Eh? Did you try IPC_STATing the message queue and obtaining the pid of the last message (msg_lrpid)?
"""The API is also quite atrocious. The only advantage over sockets is typically increased speed"""
The API offers quite a bit more flexability than sockets as well e.g. message priorities/types, persistence, etc. The Also, the atrocious API easily (and should be) be wrapped up into the equivalent of Xlib so the client would have no knowledge of the underlying IPC methods.
"""The only other choice is SysV message queues, which are connectionless and therefore difficult to use for the purposes of a display server."""
Have you tried Local Domain sockets? Or perhaps implementing a stateful protocol over the connectionless IPC?
"""Multiplexing multiple connections basically comes down to using one queue, which may lead to some issues such as any application connected to the server being able to "spoof" messages as coming from a different application."""
Eh? Did you try IPC_STATing the message queue and obtaining the pid of the last message (msg_lrpid)?
"""The API is also quite atrocious. The only advantage over sockets is typically increased speed"""
The API offers quite a bit more flexability than sockets as well e.g. message priorities/types, persistence, etc. The Also, the atrocious API easily (and should be) be wrapped up into the equivalent of Xlib so the client would have no knowledge of the underlying IPC methods.