The DBusConnection4 class provides methods for connecting to the bus, exporting objects, sending signals and getting references to remote objects.
DBusConnection is a singleton class, multiple calls to getConnection will return the same bus connection.
This creates a connection to the session bus, or returns the existing connection.
This sets up a signal handler for the given signal type. SignalHandler.handle will be called in a new thread with an instance of TestSignalInterface.TestSignal when that signal is recieved.
This sends a signal of type TestSignalInterface.TestSignal, from the object “/foo/bar/com/Wibble” with the arguments “Bar” and UInt32(42).
This exports the testclass object on the path “/Test”
This gets a reference to the “/Test” object on the process with the name “foo.bar.Test” . The object implements the Introspectable interface, and calls may be made to methods in that interface as if it was a local object.
The Runtime Exception DBusExecutionException may be thrown by any remote method if any part of the execution fails.
Calling a method on a remote object is synchronous, that is the thread will block until it has a reply. If you do not want to block you can use an asynchronous call.
There are two ways of making asynchronous calls. You can either call the callMethodAsync function on the connection object, in which case you are returned a DBusAsyncReply5 object which can be used to check for a reply and get the return value. This is demonstrated in figure 1.
Alternatively, you can register a callback with the connection using the callWithCallback function on the connection object. In this case, your callback class (implementing the CallbackHandler6 interface will be called when the reply is returned from the bus.