A named pipe is a named, one-way or duplex pipe for communication between the pipe server and one or more pipe clients. All instances of a named pipe share the same pipe name, but each instance has its own buffers and handles, and provides a separate conduit for client/server communication. The use of instances enables multiple pipe clients to use the same named pipe simultaneously.

Any process can access named pipes, subject to security checks, making named pipes an easy form of communication between related or unrelated processes.

Any process can act as both a server and a client, making peer-to-peer communication possible. As used here, the term pipe server refers to a process that creates a named pipe, and the term pipe client refers to a process that connects to an instance of a named pipe.

Named pipes can be used to provide communication between processes on the same computer or between processes on different computers across a network. If the server service is running, all named pipes are accessible remotely. If you intend to use a named pipe locally only, deny access to NT AUTHORITY\NETWORK or switch to local RPC.

For more information, see the following topics:

• Pipe Names
• Named Pipe Open Modes
• Named Pipe Type, Read, and Wait Modes
• Named Pipe Instances
• Named Pipe Operations
• Synchronous and Overlapped Input and Output
• Named Pipe Security and Access Rights
• Impersonating a Named Pipe Client
• Using Pipes

Send comments about this topic to Microsoft

Build date: 6/5/2008