Re: [gdm-list] Multi-seat and multi-display support design

[Ray Strode <halfline gmail com>]

Hi,

On Fri, Mar 13, 2009 at 9:45 AM, Dan Nicholson <dbn lists gmail com> wrote:
> On Thu, Mar 12, 2009 at 8:14 PM, Ray Strode <halfline gmail com> wrote:
>>
>> In a multiseat world, we want the X server for a given seat to only
>> open the devices that belong to that seat.  ConsoleKit is the registry
>> of seat information, so the X server may need to be changed to query
>> ConsoleKit.
>
> Since HAL (or DeviceKit) is already working with ConsoleKit, maybe it
> would make sense to put the seat information in the HAL database. So,
> you could have an integer info.seat. Then Xorg would match for
> info.seat in addition to input.x11_driver.
Could work.  Or maybe ConsoleKit should push the data to HAL instead
of HAL pulling it. Not

> Of course, at some point Xorg would need to become seat aware to make
> that reasonable. So, maybe it would work better for Xorg to listen for
> input events from HAL and then ask CK if it can use that device.
Yea that's what I was sort of thinking.

On the other hand, I don't think the X server is going to be using HAL forever.
Some people want to split HAL up into DeviceKits and udev policy, so
whatever solution we come up with, we may be changing it again the
future...

--Ray