Optional client configuration file support
Submitted by Ralf Habacker
Assigned to D-Bus Maintainers
Created attachment 118405 Add optional client configuration file support
On Windows dbus installations comes into two flavours:
- standalone dbus installer or portable installation 
- dbus bundled with 3rdparty applications 
 https://build.opensuse.org/package/show?project=home%3Arhabacker%3Abranches%3Awindows%3Amingw%3Awin32&package=mingw32-dbus-1-installer  https://build.opensuse.org/package/show?project=windows%3Amingw%3Awin32&package=mingw32-umbrello
The standalone installers provides a session bus identified by the main 'autolaunch:' meta protocol. Every client using protocol 'autolaunch:' to connect to the session bus reaches the standalone dbus installation.
DBus bundled installation can be configured to use a standalone dbus installation or the bundled dbus instance. The latter is reached with the 'autolaunch:scope=*install-path' connection string, which is required to be configured for the daemon (dbus-1.10:
<install-root>/share/dbus-1/session.conf) and all clients.
Windows applications installed by an installer are started by a start menu entry, which does not allow to provides environment variables to setup the client connection string.
With this patch the dbus message bus library could be compiled to have a client configuration file to provide the possibility for dedicated client connection string setup at one place.
The client configuration file is located at
BTW: The recent implementation uses expat to parse the xml file. Another solutions without the need to add an additional library dependency to libdbus would be to use a simple inline xml parser or to use a simple ini-style file parser (I remember that it has already been thought to simplify dbus file format)
Patch 118405, "Add optional client configuration file support":