 |
|
|
|
|
|
Inter-Process Communication in .NET Using Named Pipes, Part 2
1. Introduction
Named Pipes are sections of shared memory used by separate processes to communicate with one another. The application that creates a pipe is the pipe server. A process that connects to the pipe server is a client.
|
Download the .NET Named Pipes solution, which includes:
- A Named Pipes Wrapper
- Multithreaded Pipes Server
- Named Pipes Client
- The two parts of this article.
- AppDomain.NamedPipes reference
|
In this article we will demonstrate how to create Named Pipe server and client applications that exchange text messages. Both applications use the Named Pipes .NET implementation outlined in Part 1.
The Named Pipes server is a multithreaded engine that serves concurrent requests by creating on demand new threads and pipe connections. In addition to this, the server pipes are reused across requests in order to reduce the resource consumption on the server.
It is important to note that the situations where this solution would be most beneficial is when one application is exchanging frequent short text messages with another, located on the same machine or within the same LAN. For structured data exchange those text messages can also be XML documents or serialized .NET objects.
.NET Named Pipes Discussion
|
|
|
