gio.dbus_server.DBusServer is a helper for listening to and accepting D-Bus
connections. This can be used to create a new D-Bus server, allowing two
peers to use the D-Bus protocol for their own specialized communication.
A server instance provided in this way will not perform message routing or
implement the
`org.freedesktop.DBus` interface.
To just export an object on a well-known name on a message bus, such as the
session or system bus, you should instead use func@Gio.bus_own_name.
An example of peer-to-peer communication with GDBus can be found
in gdbus-example-peer.c.
gio.dbus_server.DBusServer is a helper for listening to and accepting D-Bus connections. This can be used to create a new D-Bus server, allowing two peers to use the D-Bus protocol for their own specialized communication. A server instance provided in this way will not perform message routing or implement the `org.freedesktop.DBus` interface.
To just export an object on a well-known name on a message bus, such as the session or system bus, you should instead use func@Gio.bus_own_name.
An example of peer-to-peer communication with GDBus can be found in gdbus-example-peer.c.
Note that a minimal gio.dbus_server.DBusServer will accept connections from any peer. In many use-cases it will be necessary to add a gio.dbus_auth_observer.DBusAuthObserver that only accepts connections that have successfully authenticated as the same user that is running the gio.dbus_server.DBusServer. Since GLib 2.68 this can be achieved more simply by passing the gio.types.DBusServerFlags.AuthenticationRequireSameUser flag to the server.