Opaque structure representing a message in the Telepathy messages interface (an array of at least one mapping from string to variant, where the
first mapping contains message headers and subsequent mappings contain the message body).
This base class provides convenience API for most of the common keys that can appear in the header. One notable exception is the sender of the
message. Inside a connection manager, messages are represented by the TpCMMessage subclass, and you should use
tp_cm_message_get_sender. When composing a message in a client using
ClientMessage, messages do not have an explicit sender (the sender
is automatically the local user). When a client sees a sent or received message signalled by the connection manager (represented by
SignalledMessage), the message's sender (if any) can be accessed
with get_sender.
Return when this message was received locally, as a number of seconds since
the beginning of 1970 in the UTC timezone (the same representation used by
DateTime.from_unix_utc, for instance), or 0 if not
known.
Return when this message was sent, as a number of seconds since the
beginning of 1970 in the UTC timezone (the same representation used by
DateTime.from_unix_utc, for instance), or 0 if not
known.
If this message is specific to a particular D-Bus interface and should be
ignored by clients without knowledge of that interface, return the name of the interface.
Returns true if this incoming message has been seen in a
previous channel during the lifetime of the Connection, but had not been acknowledged when that channel closed, causing an identical channel
(in which the message now appears) to open.