Skip to content

Support different connection family types: TCP socket, Unix domain socket and Windows named pipes

Used multiprocessing.connection.Listener supports different connection family types:

  • AF_UNIX for a Unix domain socket. Currently supported by default
  • AF_INET for a TCP socket
  • AF_PIPE for a Windows named pipe

Proposition:

  • Add an option to select different connection family type
  • By default, it should automatically use AF_UNIX on Linux/macOS and AF_PIPE on Windows

Use cases:

  • Windows support (AF_PIPE for a Windows named pipe)
  • Remote execution over network (AF_INET for a TCP socket)