We are planning to use COM+'s IConnectionPoint and IConnectionPointContainer mechanism to implement a COM server (out of process) that shall notify all the clients (windows dialog and UI developed using C++/MFC on windows) when certain changes/events occur in the system. The notification shall contain some data to be sent along with the event, which shall be a long value.
I am seeking your help to identify disadvantages of using this (COM) mechanisms over any other IPC mechanisms.
One of the other approaches that has been thrown in by others is to use windows post message mechanism instead of COM Server, so the server exe shall use post message notifications to notify all window handles interested in those events. The window handles shall be shared between client and server using some shared memory.
For COM's event mechanism I do understand that COM has abstracted all the RPC calls behind the wall for the developers for out of process servers. However if large set of data has to be shared between client and server then it could possibly become a bottleneck.
Can you please help me identify any other major concerns or disadvantages in using the COM's event mechanism approach given that all our systems shall be running on windows and on the same machine.
Thanks and regards,