In computer science, an anonymous pipe is a simplex FIFO communication channel that may be used for one-way interprocess communication (IPC). An implementation is often integrated into the operating system's file IO subsystem. Typically a parent program opens anonymous pipes, and creates a new process that inherits the other ends of the pipes, or creates several new processes and arranges them in a pipeline.
Full-duplex (two-way) communication normally requires two anonymous pipes.
Pipelines are an important part of many Unix applications and support for them is well integrated into most Unix-like operating systems. Pipes are created using the
pipe system call, which creates a new pipe and returns a pair of file descriptors referring to the read and write ends of the pipe. In a Unix shell a pipeline is created using the "
|" character and many Unix programs are designed as filters to work with pipes.
Microsoft Windows 
Like many other device IO and IPC facilities in the Windows API, anonymous pipes are created and configured with API functions that are specific to the IO facility. In this case
CreatePipe is used to create an anonymous pipe with separate handles for the read and write ends of the pipe. Read and write IO operations on the pipe are performed with the standard IO facility API functions
On Microsoft Windows, reads and writes to anonymous pipes are always blocking. In other words, a read from an empty pipe will cause the calling thread to wait until at least one byte becomes available or an end-of-file is received as a result of the write handle of the pipe being closed. Likewise, a write to a full pipe will cause the calling thread to wait until space becomes available to store the data being written. Reads may return with fewer than the number of bytes requested (also called a short read).
New processes can inherit handles to anonymous pipes in the creation process.
See also 
- Hart, Johnson M. Windows System Programming, Third Edition. Addison-Wesley, 2005. ISBN 0-321-25619-0
- "pipe(7) - Linux man page". Archived from the original on 23 March 2010. Retrieved 2010-02-27.
- "Anonymous Pipe Operations". MSDN. Retrieved 2010-02-27. "Asynchronous (overlapped) read and write operations are not supported by anonymous pipes."