From b937c4aec1b9ecf6883a714690f50e9278707e5e Mon Sep 17 00:00:00 2001
From: =?utf8?q?Marc-Andr=C3=A9=20Lureau?= <marcandre.lureau@redhat.com>
Date: Fri, 25 Mar 2022 14:45:39 +0400
Subject: [PATCH] spec: AF_UNIX now available on Windows as well
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
---
 doc/dbus-specification.xml | 14 ++------------
 1 file changed, 2 insertions(+), 12 deletions(-)

diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
index 7ebf13ff4..d256cffdf 100644
--- a/doc/dbus-specification.xml
+++ b/doc/dbus-specification.xml
@@ -3661,10 +3661,8 @@
         fields).
       </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
+        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>
@@ -3965,14 +3963,6 @@
         information on situations where these transports have been used,
         and alternatives to these transports.
       </para>
-      <para>
-        Implementations of D-Bus on Windows operating systems normally
-        use a nonce-tcp transport via the local loopback interface.
-        This is because the
-        <link linkend="transports-unix-domain-sockets">unix</link>
-        transport, which would otherwise be recommended, is not
-        available on these operating systems.
-      </para>
 
       <para>
         On start, the server generates a random 16 byte nonce and writes it
-- 
2.47.3