December 4, 2013 at 9:10 AM
Over the past couple of weeks, I have been developing real time TCP/IP communication server. The server was implemented as .Net windows service. During the development phase, it was clear that the server will require configuration application, which I decided to implement as separate application. I wanted to avoid “desktop interaction” of my service. In addition, I wanted to experiment with IPC offered by .Net framework. I have considered following IPC mechanisms:
- Windows Communication Foundation;
- .NET Remoting;
- Named Pipes;
After some testing and experimentation, I decided to develop my own IPC mechanism. Below, you will find some reasoning behind the effort.