Does named pipe bindings support crossing machine calls? [modified]
-
NetNamedPipeBinding only supports named pipes on the local machine, but if I construct a custom binding using named pipe binding, can it support crossing machine calls? As it's read in the Section 3.3.3 from the book Learning WCF:
3.3.3. NetNamedPipeBinding Features ... A named pipe enables interprocess communication both locally and remotely. The pipe is a file that can be accessed by the pipe server (the process that created the pipe) and the pipe client (the process communicating with the pipe server). The underlying path to a named pipe is a UNC path that specifies the machine name only if the pipe is remote: \\<machinename>\Pipe\<pipename> \\.\Pipe\<pipename> ...Here, looks like can enable calls from remote machines. but in the MSDN topic, Choosing a Transport:When to Use the Named Pipe Transport A named pipe is an object in the Windows operating system kernel, such as a section of shared memory that processes can use for communication. A named pipe has a name, and can be used for one-way or duplex communication between processes on a single machine.So it says, name pipes is for communication on a single machine. Thanks.modified on Friday, April 17, 2009 11:45 PM