GDBusConnection: GIO Reference Manual, GDBusConnection, Retrieves the last serial number assigned to a GDBusMessage on the current thread. This includes messages sent via both low-level API such as g_dbus_connection_send_message () as well as high-level API such as g_dbus_connection_emit_signal () , g_dbus_connection_call () or g_dbus_proxy_call ().
Retrieves the last serial number assigned to a GDBusMessage on the current thread. This includes messages sent via both low-level API such as g_dbus_connection_send_message () as well as high-level API such as g_dbus_connection_emit_signal () , g_dbus_connection_call () or g_dbus_proxy_call ().
Yes, as Michael K says, use g_dbus_connection_emit_signal(). You only have to own a well-known name if you want other users of the bus to be able to address your application by that well-known name, rather than a unique name which changes every time you connect to the bus.
The GDBusConnection type is used for D-Bus connections to remote peers such as a message buses. It is a low-level API that offers a lot of flexibility. For instance, it lets you establish a connection over any transport that can by represented as an GIOStream . This class is rarely used directly in D-Bus clients.
