Skip to content

Commit d0d6a8b

Browse files
authored
Add note about linux and IPC (#38849)
1 parent 09c0f39 commit d0d6a8b

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

docs/standard/io/how-to-use-named-pipes-for-network-interprocess-communication.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,10 @@ ms.assetid: 4e4d7e64-9f1b-4026-98f7-20488ac7b42b
1919
# How to: Use Named Pipes for Network Interprocess Communication
2020

2121
Named pipes provide interprocess communication between a pipe server and one or more pipe clients. They offer more functionality than anonymous pipes, which provide interprocess communication on a local computer. Named pipes support full duplex communication over a network and multiple server instances, message-based communication, and client impersonation, which enables connecting processes to use their own set of permissions on remote servers.
22-
22+
23+
> [!IMPORTANT]
24+
> .NET on Linux uses Unix Domain Sockets (UDS) for the implementation of these APIs.
25+
2326
To implement name pipes, use the <xref:System.IO.Pipes.NamedPipeServerStream> and <xref:System.IO.Pipes.NamedPipeClientStream> classes.
2427

2528
## Example 1

0 commit comments

Comments
 (0)