Which are the better functions to be called under windows to create processes , test exit code, interprocess communication/syncronization?
Printable View
Which are the better functions to be called under windows to create processes , test exit code, interprocess communication/syncronization?
use the API calls provided. check MSDN for the specific functions. It is nto usually beneficial to start additionl processes, just use threads.
MSDN is your reference for the Win32 API and associated MS libraries.
http://msdn.microsoft.com/en-us/libr...84(VS.85).aspx
CreateProcess() is the OS interface for process creation. IPC on windows includes shared memory, sockets, named pipes, mail slots, and few others.
http://msdn.microsoft.com/en-us/libr...74(VS.85).aspx
gg
Sending messages, WM_COPYDATA in particular, can be used for IPC as well.
If you are doign software development, it really is necessary that the customer provide you witht eh existing source code when they want features added to an application. Using one program to run another 3rd party program is generalyl considered a kludge. There are API coimmands to handle it since many applications like auto-patchers require such functionality.