a high level mechanism for the communication between processes even if they are running on different computers linked by a network
a mechanism that enables interprocess communication for applications to communicate locally or remotely
a mechanism that, not surprisingly, works like a pipe
an interprocess communication construct that allows programmatic communication between a client and a server
an interprocess communication mechanism that is similar to sockets in UNIX
a second way of performing interprocess communication (IPC)
a special case of the pipe previously described
a specifically named one-way or two-way channel for communication between a pipe server and one or more pipe clients
a static structure with the property that multiple processes can write to and/or read from it
An IPC mechanism that is implemented as a file system service, allowing programs to be modified to run on it without using a proprietary API. Named pipes were developed to support more robust client/server communications than those allowed by the simpler NetBIOS.
a UNIX pipe which is linked, as opposed to pipes used in shells. See Also pipe, link.
An interprocess communication mechanism that allows one process to send data to another local or remote process. Windows NT named pipes are not the same as Unix named pipes.
An interprocess control (IPC) protocol for exchanging information between two applications, possibly running on different computers in a network. Named Pipes are supported by a number of network operating systems.
An expanded function of a regular pipe (redirecting the output of one program to become the input of another). Instead of connecting stdout to stdin, the output of one program is sent to the named pipe and another program reads data from the same file. This is implemented through a special file known as a pipe file or fifo. The operating system ensures the proper sequencing of the data. Little or no data is actually stored in the pipe file; it just acts as a connection between the two.
An interprocess communication (IPC) mechanism that allows one process to communicate with another local or remote process.
A pipe that an application opens by name in order to write data into or read data from the pipe. By convention, named pipes are placed in the /dev directory and are treated as special files. Using a named pipe facilitates communication between a sending process and a receiving process.
A connection used to transfer data between separate processes, usually on separate computers. Named pipes are the foundation of interprocess communications and underpin Microsoft's LAN Manager Nos.
A type of interprocess communication that permits message data streams to pass between peer processes, such as between a client and a server.
A high-level interprocess communication facility that allows bidirectional, multipoint communications between processes. In an OS/2 LAN Server environment, named pipes may also be used to communicate across the LAN. Remote named pipes use NETBIOS as the underlying communications protocol.
In computing, a named pipe (also FIFO for its behaviour) is an extension to the traditional pipe concept on Unix and Unix-like systems, and is one of the methods of inter-process communication. The concept is also found in Microsoft Windows, although the semantics differ substantially. A traditional pipe is "unnamed" because it exists anonymously and persists only for as long as the process is running.
