IPC implementation method

Question

What is the preferred way to implement IPC over windows?

I know several such as: named pipe, shared memory, semaphors ?, possibly COM (although I'm not sure how) ...

I wanted to know what is considered the most reliable, fastest, least error prone and easy to maintain / understand.

Answer 1

Take a look at boost :: interprocess .

Shared memory is probably the fastest overall, but somewhat error prone and limited to local processes.

COM is fully versioned and automatically supports remote IPC, but obviously it is platform dependent.

- ActiveMQ OpenMQ.

Answer 2

/, . (UDP), . "" . . / /.

. , , 3 . 10 000 , . 4K-, .

2 6 , ( TCP).

, - , - 30% . , .

, , . , , .

, , , , . , . "". , , .

Answer 3

MSDN .

, , . Boost , - , - GUI .

Win32 (, CreatePipe , ), , , - , .

Answer 4

RPC/ COM DCOM ( RPC ) - IPC Windows, - - , , , , DCOM . :)

Answer 5

named pipe wrapping for me

for the data format, either collapse your own, or use the local RPC (which is used to use msft)