Which IPC mechanism should be used?
-
Hi all, [1]Having some 5 Client which are EXEs. And these 5 Clients need to communicate with a single Server which again is an EXE. All the clients and the single server are on same machine. [2]Clients can send some data to Server which server should store internally. [3]Clients can request some data which server should return. [4]Clients need result of executing some procedure and this procedure is in server. [5]Server need to keep track of all the client processes. Have gone through various mechanism like : [1]RPC which is robust but requires more work. [2]Named pipes [3]WM_COPYDATA Suggestion is required regarding which IPC mechanism should be used to achive all the above listed requirements. And roughly how much effort needs to be invested. Thanks.
-
Hi all, [1]Having some 5 Client which are EXEs. And these 5 Clients need to communicate with a single Server which again is an EXE. All the clients and the single server are on same machine. [2]Clients can send some data to Server which server should store internally. [3]Clients can request some data which server should return. [4]Clients need result of executing some procedure and this procedure is in server. [5]Server need to keep track of all the client processes. Have gone through various mechanism like : [1]RPC which is robust but requires more work. [2]Named pipes [3]WM_COPYDATA Suggestion is required regarding which IPC mechanism should be used to achive all the above listed requirements. And roughly how much effort needs to be invested. Thanks.
Are the 5 Clients are instances of same client EXE.
-@SuDhIrKuMaR@-
-
Are the 5 Clients are instances of same client EXE.
-@SuDhIrKuMaR@-
No. They can be of different application.
-
No. They can be of different application.
If they are different applications then you can use WM_COPYDATA.It is very easy to use.
-@SuDhIrKuMaR@-
-
Hi all, [1]Having some 5 Client which are EXEs. And these 5 Clients need to communicate with a single Server which again is an EXE. All the clients and the single server are on same machine. [2]Clients can send some data to Server which server should store internally. [3]Clients can request some data which server should return. [4]Clients need result of executing some procedure and this procedure is in server. [5]Server need to keep track of all the client processes. Have gone through various mechanism like : [1]RPC which is robust but requires more work. [2]Named pipes [3]WM_COPYDATA Suggestion is required regarding which IPC mechanism should be used to achive all the above listed requirements. And roughly how much effort needs to be invested. Thanks.
I have written software with your requirements, except that it could run on multiple networked machines. The approach I took was Named Pipes. I wrote a Generic Server, and a Generic Client, and, in effect, an RPC Procedure. In effect a 'SendMessage' procedure on the Client side, which gathered and wrapped all the Calling Info, created a Header, indicating where in the package each item resides, and, send it over the pipe. On the Server Side, you wait for the message, unwrap it, and present it to the function. For this to work, I created a MessageMap type of structure. For it to work better, Server and Client had only the Basic Bones in the Message Map for initial communication. At startup of the Client, it sends it's message map to the server, which the server registers. When you have this Generic Server/Client system written, you make each app both a server and a client. Be sure though to make plenty of use of Synchronisation Objects. N.B. The efford is always substantial, whatever route you take. I took this way because: 1. I considered RPC an overkill, and yet something else I had to learn and which Bill Gates could change on a whim. 2. Fully Debuggable, Very Few System calls you cannot debug into Regards :) Regards,
Bram van Kampen