sd-bus: Add sd_bus_send_to docs
This commit is contained in:
parent
bf39cb7b92
commit
d7fbc6804e
|
@ -388,7 +388,7 @@ manpages = [
|
||||||
'sd_bus_release_name_async',
|
'sd_bus_release_name_async',
|
||||||
'sd_bus_request_name_async'],
|
'sd_bus_request_name_async'],
|
||||||
''],
|
''],
|
||||||
['sd_bus_send', '3', [], ''],
|
['sd_bus_send', '3', ['sd_bus_send_to'], ''],
|
||||||
['sd_bus_set_address', '3', ['sd_bus_get_address', 'sd_bus_set_exec'], ''],
|
['sd_bus_set_address', '3', ['sd_bus_get_address', 'sd_bus_set_exec'], ''],
|
||||||
['sd_bus_set_close_on_exit', '3', ['sd_bus_get_close_on_exit'], ''],
|
['sd_bus_set_close_on_exit', '3', ['sd_bus_get_close_on_exit'], ''],
|
||||||
['sd_bus_set_connected_signal', '3', ['sd_bus_get_connected_signal'], ''],
|
['sd_bus_set_connected_signal', '3', ['sd_bus_get_connected_signal'], ''],
|
||||||
|
|
|
@ -138,6 +138,7 @@
|
||||||
<citerefentry><refentrytitle>sd_bus_reply_method_error</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_bus_reply_method_error</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
<citerefentry><refentrytitle>sd_bus_request_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_bus_request_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
<citerefentry><refentrytitle>sd_bus_send</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_bus_send</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
|
<citerefentry><refentrytitle>sd_bus_send_to</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
<citerefentry><refentrytitle>sd_bus_set_address</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_bus_set_address</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
<citerefentry><refentrytitle>sd_bus_set_allow_interactive_authorization</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_bus_set_allow_interactive_authorization</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
<citerefentry><refentrytitle>sd_bus_set_bus_client</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_bus_set_bus_client</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
|
|
|
@ -18,6 +18,7 @@
|
||||||
|
|
||||||
<refnamediv>
|
<refnamediv>
|
||||||
<refname>sd_bus_send</refname>
|
<refname>sd_bus_send</refname>
|
||||||
|
<refname>sd_bus_send_to</refname>
|
||||||
|
|
||||||
<refpurpose>Queue a D-Bus message for transfer</refpurpose>
|
<refpurpose>Queue a D-Bus message for transfer</refpurpose>
|
||||||
</refnamediv>
|
</refnamediv>
|
||||||
|
@ -32,35 +33,48 @@
|
||||||
<paramdef>sd_bus_message *<parameter>m</parameter></paramdef>
|
<paramdef>sd_bus_message *<parameter>m</parameter></paramdef>
|
||||||
<paramdef>uint64_t *<parameter>cookie</parameter></paramdef>
|
<paramdef>uint64_t *<parameter>cookie</parameter></paramdef>
|
||||||
</funcprototype>
|
</funcprototype>
|
||||||
|
|
||||||
|
<funcprototype>
|
||||||
|
<funcdef>int <function>sd_bus_send_to</function></funcdef>
|
||||||
|
<paramdef>sd_bus *<parameter>bus</parameter></paramdef>
|
||||||
|
<paramdef>sd_bus_message *<parameter>m</parameter></paramdef>
|
||||||
|
<paramdef>const char *<parameter>destination</parameter></paramdef>
|
||||||
|
<paramdef>uint64_t *<parameter>cookie</parameter></paramdef>
|
||||||
|
</funcprototype>
|
||||||
</funcsynopsis>
|
</funcsynopsis>
|
||||||
</refsynopsisdiv>
|
</refsynopsisdiv>
|
||||||
|
|
||||||
<refsect1>
|
<refsect1>
|
||||||
<title>Description</title>
|
<title>Description</title>
|
||||||
|
|
||||||
<para><function>sd_bus_send()</function> queues the bus message object <parameter>m</parameter>
|
<para><function>sd_bus_send()</function> queues the bus message object <parameter>m</parameter> for
|
||||||
for transfer. If <parameter>bus</parameter> is <constant>NULL</constant>, the bus that
|
transfer. If <parameter>bus</parameter> is <constant>NULL</constant>, the bus that
|
||||||
<parameter>m</parameter> is attached to is used. <parameter>bus</parameter> only needs to be set
|
<parameter>m</parameter> is attached to is used. <parameter>bus</parameter> only needs to be set when the
|
||||||
when the message is sent to a different bus than the one it's attached to, for example when
|
message is sent to a different bus than the one it's attached to, for example when forwarding messages.
|
||||||
forwarding messages. If the output parameter <parameter>cookie</parameter> is not
|
If the output parameter <parameter>cookie</parameter> is not <constant>NULL</constant>, it is set to the
|
||||||
<constant>NULL</constant>, it is set to the message identifier. This value can later be used to
|
message identifier. This value can later be used to match incoming replies to their corresponding
|
||||||
match incoming replies to their corresponding messages. If <parameter>cookie</parameter> is set
|
messages. If <parameter>cookie</parameter> is set to <constant>NULL</constant> and the message is not
|
||||||
to <constant>NULL</constant> and the message is not sealed, <function>sd_bus_send()</function>
|
sealed, <function>sd_bus_send()</function> assumes the message <parameter>m</parameter> doesn't expect a
|
||||||
assumes the message <parameter>m</parameter> doesn't expect a reply and adds the necessary
|
reply and adds the necessary headers to indicate this.</para>
|
||||||
headers to indicate this.</para>
|
|
||||||
|
|
||||||
<para>Note that in most scenarios, <function>sd_bus_send()</function> should not be called
|
<para>Note that in most scenarios, <function>sd_bus_send()</function> should not be called
|
||||||
directly. Instead, use higher level functions such as
|
directly. Instead, use higher level functions such as
|
||||||
<citerefentry><refentrytitle>sd_bus_call_method</refentrytitle><manvolnum>3</manvolnum></citerefentry> and
|
<citerefentry><refentrytitle>sd_bus_call_method</refentrytitle><manvolnum>3</manvolnum></citerefentry> and
|
||||||
<citerefentry><refentrytitle>sd_bus_reply_method_return</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>sd_bus_reply_method_return</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
||||||
which call <function>sd_bus_send()</function> internally.</para>
|
which call <function>sd_bus_send()</function> internally.</para>
|
||||||
|
|
||||||
|
<para><function>sd_bus_send_to()</function> is a shorthand for sending a message to a specific
|
||||||
|
destination. It's main use case is to simplify sending unicast signal messages (signals that only have a
|
||||||
|
single receiver). It's behavior is similar to calling
|
||||||
|
<citerefentry><refentrytitle>sd_bus_message_set_destination</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
||||||
|
followed by calling <function>sd_bus_send()</function>.</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
<refsect1>
|
<refsect1>
|
||||||
<title>Return Value</title>
|
<title>Return Value</title>
|
||||||
|
|
||||||
<para>On success, this function returns a non-negative integer. On failure, it returns a
|
<para>On success, these functions return a non-negative integer. On failure, they return a negative
|
||||||
negative errno-style error code.</para>
|
errno-style error code.</para>
|
||||||
|
|
||||||
<refsect2 id='errors'>
|
<refsect2 id='errors'>
|
||||||
<title>Errors</title>
|
<title>Errors</title>
|
||||||
|
@ -85,8 +99,8 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><constant>-ECHILD</constant></term>
|
<term><constant>-ECHILD</constant></term>
|
||||||
|
|
||||||
<listitem><para>The bus connection was allocated in a parent process and is being reused
|
<listitem><para>The bus connection was allocated in a parent process and is being reused in a child
|
||||||
in a child process after <function>fork()</function>.</para></listitem>
|
process after <function>fork()</function>.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
@ -128,8 +142,7 @@
|
||||||
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
<citerefentry><refentrytitle>sd_bus_call_method</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_bus_call_method</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
<citerefentry><refentrytitle>sd_bus_message_set_destination</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_bus_message_set_destination</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
<citerefentry><refentrytitle>sd_bus_reply_method_return</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_bus_reply_method_return</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
||||||
<citerefentry><refentrytitle>sd_bus_send_to</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
|
||||||
</para>
|
</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue