DBusConnection.callWithUnixFdList

void callWithUnixFdList(string busName, string objectPath, string interfaceName, string methodName, glib.variant.Variant parameters, glib.variant_type.VariantType replyType, gio.types.DBusCallFlags flags, int timeoutMsec, gio.unix_fdlist.UnixFDList fdList = null, gio.cancellable.Cancellable cancellable = null, gio.types.AsyncReadyCallback callback = null)

Like [gio.dbus_connection.DBusConnection.call] but also takes a #GUnixFDList object.

The file descriptors normally correspond to G_VARIANT_TYPE_HANDLE values in the body of the message. For example, if a message contains two file descriptors, fd_list would have length 2, and g_variant_new_handle (0) and g_variant_new_handle (1) would appear somewhere in the body of the message (not necessarily in that order!) to represent the file descriptors at indexes 0 and 1 respectively.

When designing D-Bus APIs that are intended to be interoperable, please note that non-GDBus implementations of D-Bus can usually only access file descriptors if they are referenced in this way by a value of type G_VARIANT_TYPE_HANDLE in the body of the message.

This method is only available on UNIX.

Parameters

busNamea unique or well-known bus name or null if connection is not a message bus connection
objectPathpath of remote object
interfaceNameD-Bus interface to invoke method on
methodNamethe name of the method to invoke
parametersa #GVariant tuple with parameters for the method or null if not passing parameters
replyTypethe expected type of the reply, or null
flagsflags from the #GDBusCallFlags enumeration
timeoutMsecthe timeout in milliseconds, -1 to use the default timeout or G_MAXINT for no timeout
fdLista #GUnixFDList or null
cancellablea #GCancellable or null
callbacka #GAsyncReadyCallback to call when the request is satisfied or null if you don't * care about the result of the method invocation