Passing file descriptors over DBUS

[Jim Gettys]

The basic idea is to have the desktop initially in control of all input
devices (hotplug can do its thing), be able to query the user as to
whether to add them to the X server, and if so, then pass the open file
descriptor to the X server.

We want to get away to X being in direct control of devices; they may be
needed for stand alone use or for use with X servers on other machines.
This can also solve the "dueling X server config file" disaster on
multi-seat configurations.

X is a server; it should do what it is told, not believe it is the
center of the device universe.
				- Jim


On Thu, 2005-09-08 at 08:47 -0400, Havoc Pennington wrote:
> On Thu, 2005-09-08 at 12:48 +0200, Waldo Bastian wrote:
> > 
> > > The system bus is already used to obtain network configuration for
> > > example (in NetworkManager), so there may be a way to use that same
> > > approach.
> > 
> > Huh? I fail to see the relation between the two, but then again, I never 
> > looked very closely to the NetworkManager. Any particular code I should look 
> > at?
> 
> I don't know what you are doing in detail so I don't know if it relates.
> The way NetworkManager works as I remember it is that the user's session
> owns a service on the system bus which can be queried for the desired
> network configuration. The system bus is intended to be an
> authenticated/secure communication channel. Doing something similar for
> some X config makes sense to me, but it depends on what you are doing
> exactly.
> 
> Havoc
> 
> 
> _______________________________________________
> dbus mailing list
> dbus at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dbus