Next: UDP sockets, Previous: TCP sockets, Up: Client connections [Contents][Index]
The pipe implementation supports both named and anonymous pipes. Pipe servers are implemented as listeners on a file system FIFO on Unices or “Named Pipes” on Windows (can be shared over a Windows network).
A FIFO special file is similar to a pipe, except that it is created in a different way. Instead of being an anonymous communications channel, a FIFO special file is entered into the file system.
Once you have created a FIFO special file in this way, any process can open it for reading or writing, in the same way as an ordinary file. However, it has to be open at both ends simultaneously before you can proceed to do any input or output operations on it.
Create a socket structure containing both the pipe descriptors
recv_fd and send_fd. Return NULL
on errors.
Create a (non blocking) pair of pipes. This differs in Win32 and Unices. Return a non-zero value on errors.
Create a pipe connection socket structure to the pair of named
pipes recv and send. Return NULL
on errors.
Return 1 if handle is invalid, otherwise 0.
Invalidate the handle pointed at by href.
Close handle. Return 0 if successful, -1 otherwise.
Next: UDP sockets, Previous: TCP sockets, Up: Client connections [Contents][Index]