Yeah. Recent dbus api's add DbusObjectManager support to export a collection of things, e.g. sessions in our case, which then can have trees of objects underneath.
So I'd like to see Sessions exported as DbusObjectManager with jobs/instances under each on the session bus.
But, wouldn't each session have it's own D-Bus session bus? such that actually there is 1-to-1 mapping between upstart sessions and Dbus Session buses?
Yeah. Recent dbus api's add DbusObjectManager support to export a collection of things, e.g. sessions in our case, which then can have trees of objects underneath.
So I'd like to see Sessions exported as DbusObjectManager with jobs/instances under each on the session bus.
But, wouldn't each session have it's own D-Bus session bus? such that actually there is 1-to-1 mapping between upstart sessions and Dbus Session buses?