spec: Recommend Unix domain sockets for all non-Windows platforms

Bug: https://bugs.freedesktop.org/show_bug.cgi?id=106004
Signed-off-by: Simon McVittie <smcv@collabora.com>
Reviewed-by: Ralf Habacker <ralf.habacker@freenet.de>
Reviewed-by: Philip Withnall <withnall@endlessm.com>

diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
index 3b2be1c3445cf0f816570a0172d311a55faadeaa..14fac9ee64116b6701ec3372886a2326d95de2c0 100644 (file)
--- a/doc/dbus-specification.xml
+++ b/doc/dbus-specification.xml
@@ -3543,6 +3543,10 @@
       </para>
       <para>
         Unix domain sockets are not available on Windows.
+        On all other platforms, they are the recommended transport for
+        D-Bus, either used alone or in conjunction with
+        <link linkend="transports-systemd">systemd</link> or
+        <link linkend="transports-launchd">launchd</link> addresses.
       </para>
       <para>
         Unix addresses that specify <literal>path</literal> or
@@ -3691,7 +3695,8 @@
       </para>
       <para>
         The systemd transport accepts only one or more Unix domain or
-        TCP streams sockets passed in via socket activation.
+        TCP streams sockets passed in via socket activation. Using
+        Unix domain sockets is strongly recommended.
       </para>
       <para>
         The systemd transport is not available on non-Linux operating systems.