Closes connection. Note that this never causes the process to
exit (this might only happen if the other end of a shared message
bus connection disconnects, see "exit-on-close").
Once the connection is closed, operations such as sending a message
will return with the error G_IO_ERROR_CLOSED. Closing a connection
will not automatically flush the connection so queued messages may
be lost. Use g_dbus_connection_flush() if you need such guarantees.
If connection is already closed, this method fails with
G_IO_ERROR_CLOSED.
When connection has been closed, the "closed"
signal is emitted in the thread-default main
loop of the thread that connection was constructed in.
This is an asynchronous method. When the operation is finished,
callback will be invoked in the thread-default main
loop of the thread you are calling this method from. You can
then call g_dbus_connection_close_finish() to get the result of the
operation. See g_dbus_connection_close_sync() for the synchronous
version.
Since 2.26
Closes connection. Note that this never causes the process to exit (this might only happen if the other end of a shared message bus connection disconnects, see "exit-on-close"). Once the connection is closed, operations such as sending a message will return with the error G_IO_ERROR_CLOSED. Closing a connection will not automatically flush the connection so queued messages may be lost. Use g_dbus_connection_flush() if you need such guarantees. If connection is already closed, this method fails with G_IO_ERROR_CLOSED. When connection has been closed, the "closed" signal is emitted in the thread-default main loop of the thread that connection was constructed in. This is an asynchronous method. When the operation is finished, callback will be invoked in the thread-default main loop of the thread you are calling this method from. You can then call g_dbus_connection_close_finish() to get the result of the operation. See g_dbus_connection_close_sync() for the synchronous version. Since 2.26