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.
Well most applications INCLUDING Gtk+ use a select()/poll() call to wait on the socket descriptor from the X server.
I should read before responding. I was assuming you were talking about multiplexing connections on the server end.
NeXT/Apple handled event muxing through a complex run loop event processing system. In OS X this is implemented as part of CoreFoundation in Run Loop Services, which provide an easy broadcast model interface for registering and unregistering events which you wish to be notified about. This includes, but is not limited to, Mach events, sockets, and timers.
I should also add X currently utilizes sockets and shared memory, but the way this was accomplished was less-than-ideal
Well most applications INCLUDING Gtk+ use a select()/poll() call to wait on the socket descriptor from the X server.
I should read before responding. I was assuming you were talking about multiplexing connections on the server end.
NeXT/Apple handled event muxing through a complex run loop event processing system. In OS X this is implemented as part of CoreFoundation in Run Loop Services, which provide an easy broadcast model interface for registering and unregistering events which you wish to be notified about. This includes, but is not limited to, Mach events, sockets, and timers.
I should also add X currently utilizes sockets and shared memory, but the way this was accomplished was less-than-ideal