[patch] direct service connections

Havoc Pennington hp at redhat.com
Sat Nov 6 08:46:05 PST 2004

On Fri, 2004-11-05 at 00:04 -0500, Colin Walters wrote:
> Although I am thinking now it would still be useful to have
> DBUS_BUS_SESSION_LOCAL, so Imsep doesn't become insanely slow on thin
> client setups.

How do we start that and manage its lifecycle? Maybe it's slaved to the
sessionwide bus?

If you define that each session has a bus for the whole session, and
then child buses for each machine involved in the session, then you need
some way to identify which machines there are.

One possibility is come up with a way to have a guid per machine.

Another possibility is something like:
 - session bus creates a guid for the session
 - the session-machine bus listens on a socket whose name can be 
   created from the guid
 - you can thus ensure there's only one session-machine bus per session-
   machine pair by checking existence of the socket from the app's 
   filesystem namespace
 - the session-machine bus connects to the session bus and exits
   when the session bus does
However, in this possibility I don't know who fork/execs the 
session-machine bus. It sort of has to be the app, but that introduces
certain annoying issues (and more logic than desired in libdbus)


More information about the dbus mailing list