tp_text_channel_send_message_async ()

Submit a message to the server for sending. Once the message has been
submitted to the sever, callback
will be called. You can then call
tp_text_channel_send_message_finish() to get the result of the operation.

tp_text_channel_send_message_finish ()

token
can be used to match any incoming delivery or failure reports
against the sent message. If this function returns true but the returned
token is NULL, the message was sent successfully but the protocol does not
provide a way to identify it later.

A message should be acknowledged once it has been shown to the user by the
Handler of the channel. So Observers and Approvers should NOT acknowledge
messages themselves.
Once a message has been acknowledged, it is removed from the
pending-message queue and so the “pending-message-removed”
signal is fired.

tp_text_channel_get_sms_length_async ()

Starts an async call to get the number of 140 octet chunks required to
send a message via SMS on self, as well as the number of remaining
characters available in the final chunk and, if possible,
an estimate of the cost.

Parameters

if not NULL used to return
the number of 140 octet chunks required to send the message.

[out]

remaining_characters

if not NULL used to return
the number of further characters that can be fit in the final chunk.
A negative value indicates that the message will be truncated by
abs(remaining_characters
).
The value G_MININT32 indicates the message will be truncated by
an unknown amount.

[out]

estimated_cost

if not NULL used to return
the estimated cost of sending this message.
The currency and scale of this value are the same as the
values of the “balance-scale” and
“balance-currency” properties.
A value of -1 indicates the cost could not be estimated.