Two threads in different processes
-
It's said that if two threads in different processes communicate with each other, a window must be there for the sake of a message called WM_COPYDATA. My question is: Without any window, can these two threads communicate with each other, and how? Best regard :rose: Best regard. I confess that I am a stubborn guy, but why not put things thoroughly, logically and systematically clean. One concrete prolem is worth a thousand unapplied abstractions.
-
It's said that if two threads in different processes communicate with each other, a window must be there for the sake of a message called WM_COPYDATA. My question is: Without any window, can these two threads communicate with each other, and how? Best regard :rose: Best regard. I confess that I am a stubborn guy, but why not put things thoroughly, logically and systematically clean. One concrete prolem is worth a thousand unapplied abstractions.
If the target thread/process does not have a window then WM_COPYDATA is not an option for you. If it is only simple data you can try using the clipboard, though you can't notify the target thread. It'll have to keep checking the clipboard on it's own. I guess you can try memory mapped files [a topic I know nothing about] Nish
_
If I am awake and my eyes are closed, it does not necessarily mean that I am thinking of naked women._
-
It's said that if two threads in different processes communicate with each other, a window must be there for the sake of a message called WM_COPYDATA. My question is: Without any window, can these two threads communicate with each other, and how? Best regard :rose: Best regard. I confess that I am a stubborn guy, but why not put things thoroughly, logically and systematically clean. One concrete prolem is worth a thousand unapplied abstractions.
The following possibilities spring to mind... * mutex/event if only signalling is required * Memory mapped files(I seem to recall a rather nice tutorial on this site somewhere) *Sockets *Local RPC (You need to understand IDL) *Named pipes (Similar in concept to sockets) *DCOM I'd probably use sockets myself, because that's what I'm most familiar with. Rob.