Re: About Process Communication Implementation in Windows.

On Oct 19, 12:27 pm, "Günter Prossliner" <g.prossliner/gmx/at> wrote:
Hello

In the book< Programming Application for miscrosoft windows>

Which book is this? You you have a link?

These mechanisms[note:Process communication] include RPC, COM, OLE,
DDE, window messages (especially WM_COPYDATA), the clipboard,
mailslots, pipes, sockets, and so on. In Windows, the lowest-level
mechanism for sharing data on a single machine is the memory-mapped
file. That's right, all of the mechanisms I mention ultimately use
memory-mapped files to do their dirty work if all the processes
communicating are on the same machine.

Many of them (e.g. COM, OLE) are based on RPC. I don't know if local RPC is
implemented with memory mapped files.

WM_COPYDATA, DDE, (local) pipes and the Clipboard ist AFAIK implemented by
m. m. f..

But sockets are a different technology (Networking Stack).

GP

RPC is also based on memory mapped files.

.

Relevant Pages

  • Re: About Process Communication Implementation in Windows.
    ... DDE, window messages, the clipboard, ... WM_COPYDATA, DDE, pipes and the Clipboard ist AFAIK implemented by ... But sockets are a different technology. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Why 64bit Delphi compiler from Borland may be meaningless!
    ... pipes, sockets, memory mapped files, COM. ... 64-bit version of Windows that will allow 64-bit user mode code to call ...
    (borland.public.delphi.non-technical)
  • Re: WM_COPYDATA,...
    ... Certainly NOT the clipboard. ... It doesn't really matter. ... mapped into the recipient's address space, and deleted when you return from handling the ... to avoid this, use memory mapped files. ...
    (microsoft.public.vc.mfc)