Support for UNIX-domain (also known as local) sockets, corresponding to
struct sockaddr_un.
UNIX domain sockets are generally visible in the filesystem.
However, some systems support abstract socket names which are not
visible in the filesystem and not affected by the filesystem
permissions, visibility, etc. Currently this is only supported
under Linux. If you attempt to use abstract sockets on other
systems, function calls may return gio.types.IOErrorEnum.NotSupported
errors. You can use gio.unix_socket_address.UnixSocketAddress.abstractNamesSupported
to see if abstract names are supported.
Since GLib 2.72, gio.unix_socket_address.UnixSocketAddress is available on all platforms. It
requires underlying system support (such as Windows 10 with AF_UNIX) at
run time.
Before GLib 2.72, <gio/gunixsocketaddress.h> belonged to the UNIX-specific
GIO interfaces, thus you had to use the gio-unix-2.0.pc pkg-config file
when using it. This is no longer necessary since GLib 2.72.
Support for UNIX-domain (also known as local) sockets, corresponding to struct sockaddr_un.
UNIX domain sockets are generally visible in the filesystem. However, some systems support abstract socket names which are not visible in the filesystem and not affected by the filesystem permissions, visibility, etc. Currently this is only supported under Linux. If you attempt to use abstract sockets on other systems, function calls may return gio.types.IOErrorEnum.NotSupported errors. You can use gio.unix_socket_address.UnixSocketAddress.abstractNamesSupported to see if abstract names are supported.
Since GLib 2.72, gio.unix_socket_address.UnixSocketAddress is available on all platforms. It requires underlying system support (such as Windows 10 with AF_UNIX) at run time.
Before GLib 2.72, <gio/gunixsocketaddress.h> belonged to the UNIX-specific GIO interfaces, thus you had to use the gio-unix-2.0.pc pkg-config file when using it. This is no longer necessary since GLib 2.72.