| Named Pipe |
Article Index for Named |
Website Links For Named |
Information AboutNamed Pipe |
| CATEGORIES ABOUT NAMED PIPE | |
| inter-process communication | |
|
NAMED PIPES IN UNIX Instead of a conventional, unnamed, shell pipeline, a named pipeline is explicitly created using mknod or mkfifo , and two separate processes can access the pipeline by name. For example, one can create a pipe and set up gzip to compress things piped to it mkfifo pipe gzip -9 -c < pipe > out in a separate process, independently, one could perform cat file > pipe which would then perform the compression by gzip. NAMED PIPES IN WINDOWS In Windows, the design of named pipes is based towards ). Named pipes aren't permanent and can't be created as special files on any writable filesystem, unlike in Unix, but are volatile names (freed after the last reference to them is closed) allocated in the root directory of the named pipe filesystem (NPFS), mounted under the special path \.\pipe\ (that is, a pipe named " Foo " would have a full path name of \.\pipe oo). Anonymous pipes used in pipelining actually are named pipes with a random name. They are very rarely seen by users, but there are notable exceptions. The VMware Workstation PC hardware virtualization tool, for instance, can expose emulated Serial Port s to the host system as named pipes, and the Kd kernel mode Debugger from Microsoft supports named pipes as a transport for debugging sessions (in fact, VMware and kd can be coupled together - since kd normally requires a serial connection to the target computer - letting Driver Developer s do their development and testing on a single Computer ). Both programs require the user to enter names in the \.\pipe\''name'' form. Windows NT Named Pipes can inherit a security context. NAMED PIPES IN WINDOWS NETWORKING Named Pipes is also a networking protocol in the Server Message Block (SMB) suite, based on the use of a special Inter-process Communication (IPC) share. SMB's IPC can seamlessly and transparently pass the authentication context of the user across to Named Pipes. Windows NT's entire NT Domain protocol suite of services are implemented as DCE/RPC services over Named Pipes, as are the Exchange 5.5 Administrative applications. Windows NT Named Pipe authentication inheritance is sufficiently opaque and seamless to the user and developer perspective as to be nearly invisible, and consequently it is frequently misunderstood. SEE ALSO EXTERNAL LINKS
|
|
|