Lines Matching full:sent
1173 (which implies sent in the <literal>METHOD_CALL</literal>), or "out" (which implies
1175 "inout" arguments, which are both sent and received, i.e. the caller
1379 In examples, "C:" and "S:" indicate lines sent by the client and
1423 sockets. However, the nul byte must be sent even on other kinds of
1425 sent in order to transmit credentials. The text protocol described in
1435 The credentials sent along with the nul byte may be used with the
1466 an OK command must be sent to the client.
1544 after the OK command has been sent.
1563 If an ERROR is sent, the server or client that sent the
2382 usual. It does not matter which object path a ping is sent to. The
2394 It does not matter which object path a GetMachineId is sent to. The
2642 Signals normally do not specify a destination; they are sent to all
2660 the ping message were sent with a <literal>DESTINATION</literal> name of
2688 categorically prevents "spoofing"; messages sent to a unique name
2755 This method call should be sent to
2990 This method call should be sent to
3048 rules. Match rules describe what messages can be sent to a client
3090 <entry>Match messages sent by a particular sender. An example of a sender match
3096 <entry>Match messages sent over or to a particular interface. An example of an
3110 <entry>Matches messages which are sent from or to the given object. An example of a
3116 <entry>Matches messages which are being sent to the given unique name. An
3210 timeout, an error should be sent back.]
3531 This signal is sent to a specific application when it loses
3564 This signal is sent to a specific application when it gains
3935 Each bus name has a primary owner; messages sent to the name go to the
