Re: interprocess communication
- From: "Voidcoder" <voidcoder@xxxxxxxxx>
- Date: Tue, 16 Aug 2005 17:35:05 -0700
The fastest way of course is shared memory. Just reserve
some space in config.bib and then use MmMapIoSpace
or VirtualAlloc/Copy to receive a pointer to this buffer
from two and more apps.
Another way (a bit slowly, but not so dirty) is FileMapping.
Use CreateFileForMapping,CreateFileMapping,
MapViewOfFile to create file mapping and access shared
buffer.
Create a hidden window in one app, and then use
FindWindow to obtain window handle and then
send data using a custom message (eg. UM_USER + something).
You may also want to use WM_COPYDATA message, however
this requre to have a window (at least hidden one).
Btw HWND_BROADCAST works ok on any windows
platform, should be something wrong with Your code. BUT
note You can not pass more than 8 bytes (WPARAM+LPARAM)
at once using HWND_BROADCAST or just any custom message.
Use WM_COPYDATA instead to pass more than 8 bytes
at a time.
"Ozb" <ozgurbali@xxxxxxxxxxx> wrote in message news:OEOUW7ioFHA.2472@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> Is there any sample of messaging between two distinct process(xx.exe and
> device.exe).
>
> I tried postmessage with HWND_:BROADCAST parameter but I could not managed
> to get the message with
> PeekMessage..
>
> What are the other ways of interprocess communication??
> like filemapping, virtual memory, which gives best performence, does anyone
> benchmarked in range miliseconds.
>
> Thanks...
> Ozby
>
>
>
>
.
- References:
- interprocess communication
- From: Ozb
- interprocess communication
- Prev by Date: Re: Debugging in ROM
- Next by Date: error using malloc with GetSystemTime
- Previous by thread: Re: interprocess communication
- Next by thread: Error when using malloc
- Index(es):
Relevant Pages
|
