ChannelRequest
Object Hierarchy:
Description:
[ Version ( since = "0.7.32" ) ]
public class ChannelRequest : Proxy
Requesting a channel from the channel dispatcher can take some time, so an object is created in the channel dispatcher to represent each request.
This proxy represents one of those objects.
Any client can call tp_cli_channel_request_call_cancel
at any time to attempt to cancel the request.
On success, the succeeded signal will be emitted.
Immediately after that, the invalidated signal will be
emitted, with the domain TP_DBUS_ERRORS
and the error code
OBJECT_REMOVED (this is not an error condition, it
merely indicates that the channel request no longer exists).
On failure, the invalidated signal will be emitted with some other suitable error, usually from the Error domain.
If the channel dispatcher crashes or exits, the invalidated
signal will be emitted with the domain TP_DBUS_ERRORS
and the error code
NAME_OWNER_LOST.
Creating a ChannelRequest directly is deprecated: it should only be created via a AccountChannelRequest or a BaseClient.
Since 0.16, ChannelRequest always has a non-%NULL factory, and its factory will be propagated to the Account, Connection and Channel.