I've done some thinking. It's really radical what I suggest,
but to solve this, you should get another dbus step
one for the system
one for every user on that system
one for every session of that user
now the situation is:
one for the system
one for every session on that system
Normaly (99% of the cases) a user has one session going, (so there is a
one-on-one match between the user and the session)
but sometimes a user has more sessions
(and there is a one to many relation)
Sessiondependend things rely on the sessionpart (X windows),
userdependend things (like addresbookconfiguration) rely on the userpart.
I'm afraid that this is the only sollution: it makes the whole dbus thing much
more comlicated.
Stef Bon
Voorburg
The Netherlands
_______________________________________________
dbus mailing list
dbus-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@xxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dbus
|
