Hello, I am really liking the approach multi-seat support is taking. Thanks for your good work. <div class="gmail_quote"><div> Like I said on a previous email I am working on a NX Server. This server basically stores parameters and manipulates the session using these parameters. It has some shortcommings. - Seat should contain a seattype. When I add a seat for NX, gdm don't need to connect to this seat SessionToAdd signal. - The session id should contain the hostname as prefix. I want it for load balance. Like LocalhostSession1 About the generic parameters: - A way to set these parameters. NX allows reconnection to a running X server, and it can change the parameters. (example: compression, connection link type(speed), shares, others). - ConsoleKit should not pass every parameter using signal, ssid is enough (maybe exec too). GetParameters on the session object is the correct approach. This way we can keep sensitive information. I think the session leader approach should be redesigned. - A session leader should listen to one or more seattypes. - Session leader should have a valid dbus service. - Session leader validation should be done using the dbus service owner instead of the pid. This means that a session can be closed by the leader not by the pid that launched it. </div></div>Regards.