Re: Reliability of WM_COPYDATA in Processing Data between Applications,...

From:

"Tom Serface" <tom.nospam@camaswood.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Wed, 21 Nov 2007 08:10:03 -0800

Message-ID:

<E1AABE47-5FA1-4EE0-B810-E84ECF78A1C0@microsoft.com>

I've never had a problem with this mechanism and it seems to happen almost
instantly (as instant as a computer can be). If you are passing a string
you have to make sure the string is available while the data is being
processed. I typically just pass a pointer to a class member that I know
will be available to the program handling the message. I guess the limit
would be like any other memory limit.

I also find this a lot easier to implement than some of the alternative
methods of doing the same thing.

Tom

"Kerem GLmrLkcL" <kareem114@hotmail.com> wrote in message
news:eTd$txBLIHA.1324@TK2MSFTNGP06.phx.gbl...

Hi,

my questions are straight: How reliable is WM_COPYDATA if
i want to send "static" data, of cource no pointers or refrences?
Is there a Memory Size limitation in theory and in real life? How
fast is this (sure depending on cpu, memory and allover system
performance)?

I never used that message before when i wanted to transfer data
between applications. I always used some sort of ipc, sockets, pipes
IOCTRL, etc,...since they are the best reliable methods available...

Anybody has experience with this WM_COPYDATA?

Regards

Kerem

--
-----------------------
Beste GrLsse / Best regards / Votre bien devoue
Kerem GLmrLkcL
kerem.g@arcor.de

Best Quote: "Ain't nobody a badass with a double dose
of rock salt...", Kill Bill Vol.2

Microsoft Live Space: http://kerem-g.spaces.live.com/
Latest Open-Source Projects: http://entwicklung.junetz.de
Sign my guestbook: http://entwicklung.junetz.de/guestbook/
-----------------------
"This reply is provided as is, without warranty express or implied."