Communication Between or Among Separate Running Programs

[dedndave]

...Suppose my program crashes into a loop that does nothing but broadcast the same message repeatedly as
fast as the os can process the SendMessages.  Mightn't that clog the other processes' message queues?

reminds me of a doctor story...

Patient: "Doc, it hurts when i bend my elbow like this"
Doctor: "Then, don't do that"

:P

[ToutEnMasm]

To redskull,

Real Men(tm) use COM 

I have folowed the link and find

IDataObject Interface
Enables data transfer and notification of changes in data. Data
transfer methods specify the format of the transferred data along
with the medium through which the data is to be transferred.
Optionally, the data can be rendered for a specific target device.
In addition to methods for retrieving and storing data,
the IDataObject interface specifies methods for enumerating available
formats and managing connections to advisory sinks for handling change
notifications.

The term data object is used to mean any object that supports an
implementation of the IDataObject interface. Implementations vary,
depending on what the data object is required to do; in some data

The implementation of the IDataObject interface is  big work .
Perhaps as a real men can you just post it  :P

[redskull]

Perhaps as a real men can you just post it  :P

In assembly?  I wish I were that manly... :'(

[PBrennick]

Remember this. Don't use COM when there is no need to. (Of course if you like to beat yourself up ...)  ::)

Paul

[raleeper]

reminds me of a doctor story...

Patient: "Doc, it hurts when i bend my elbow like this"
Doctor: "Then, don't do that"

:P

Yes.  My other favorite doctor story is:

(Doctor examining patient)
Either you ain't got no pulse, or my watch has stopped)

{credit: Groucho Marx, Walt Kelly}

I can think of some cases where that might be apropos.