20.2 Windows Pipes
As mentioned earlier, you can also benefit from the communication between applications via the file system on your Windows system. In this case, Windows pipes are used instead of Unix sockets. The difference becomes most obvious in the naming of the resource. On Unix systems with Unix sockets, you only need to specify a path to a file. To use Windows pipes, you must follow a special naming convention. The path to a pipe consists of the server name, the pipe keyword, and a name for the pipe that you can freely choose. The backslash is used as a separator. If you want to communicate locally, you just need to specify a point instead of a server name. Listing 20.8 shows how you can use a pipe on Windows to create a socket server. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access