D-Bus windows help

Alexander Larsson alexl at redhat.com
Wed Jul 11 12:39:16 PDT 2012

On Tue, 2012-07-03 at 15:16 +0100, Simon McVittie wrote:
> On 03/07/12 14:51, Jesper Dam wrote:
> > You may find it a lot easier to get started if you use autolaunch: as
> > your dbus address, instead of nonce-tcp.
> If you know how autolaunching on Windows works/is meant to work, your
> comments on <https://bugs.freedesktop.org/show_bug.cgi?id=38201> would
> be very much appreciated.
> I'd particularly like to know what the advantages and disadvantages of
> autolaunch:, autolaunch:scope=*user and autolaunch:scope=*install-path
> are, and how an application distributor should choose which one to use,
> so we can make an informed decision about which one should be the D-Bus
> default.
> There are also two patches awaiting review on that bug which change the
> default address on Windows to "autolaunch:scope=*install-path" (it'd be
> easy to switch to plain "autolaunch:" if that's more desirable).

GDbus on win32 doesn't support any of the scopes. install-path for
instance doesn't seem to be a great choice for gdbus as it ties the
implementation-independent protocol to an implementation (and gdbus is a
non-libdbus client implementation).

More information about the dbus mailing list