|
JUCE
|
Acts as the slave end of a master/slave pair of connected processes. More...
Public Member Functions | |
| ChildProcessSlave () | |
| Creates a non-connected slave process. More... | |
| virtual | ~ChildProcessSlave () |
| Destructor. More... | |
| bool | initialiseFromCommandLine (const String &commandLine, const String &commandLineUniqueID, int timeoutMs=0) |
| This checks some command-line parameters to see whether they were generated by ChildProcessMaster::launchSlaveProcess(), and if so, connects to that master process. More... | |
| virtual void | handleMessageFromMaster (const MemoryBlock &)=0 |
| This will be called to deliver messages from the master process. More... | |
| virtual void | handleConnectionMade () |
| This will be called when the master process finishes connecting to this slave. More... | |
| virtual void | handleConnectionLost () |
| This will be called when the connection to the master process is lost. More... | |
| bool | sendMessageToMaster (const MemoryBlock &) |
| Tries to send a message to the master process. More... | |
Acts as the slave end of a master/slave pair of connected processes.
The ChildProcessSlave and ChildProcessMaster classes make it easy for an app to spawn a child process, and to manage a 2-way messaging connection to control it.
To use the system, you need to create subclasses of both ChildProcessSlave and ChildProcessMaster. To instantiate the ChildProcessSlave object, you must add some code to your main() or JUCEApplication::initialise() function that calls the initialiseFromCommandLine() method to check the app's command-line parameters to see whether it's being launched as a child process. If this returns true then the slave process can be allowed to run, and its handleMessageFromMaster() method will be called whenever a message arrives.
The juce demo app has a good example of this class in action.
| ChildProcessSlave::ChildProcessSlave | ( | ) |
Creates a non-connected slave process.
Use initialiseFromCommandLine to connect to a master process.
|
virtual |
Destructor.
| bool ChildProcessSlave::initialiseFromCommandLine | ( | const String & | commandLine, |
| const String & | commandLineUniqueID, | ||
| int | timeoutMs = 0 |
||
| ) |
This checks some command-line parameters to see whether they were generated by ChildProcessMaster::launchSlaveProcess(), and if so, connects to that master process.
In an exe that can be used as a child process, you should add some code to your main() or JUCEApplication::initialise() that calls this method.
The commandLineUniqueID should be a short alphanumeric identifier (no spaces!) that matches the string passed to ChildProcessMaster::launchSlaveProcess().
The timeoutMs parameter lets you specify how long the child process is allowed to run without receiving a ping from the master before the master is considered to have died, and handleConnectionLost() will be called. Passing <= 0 for this timeout makes it use a default value.
Returns true if the command-line matches and the connection is made successfully.
|
pure virtual |
This will be called to deliver messages from the master process.
The call will probably be made on a background thread, so be careful with your thread-safety! You may want to respond by sending back a message with sendMessageToMaster()
|
virtual |
This will be called when the master process finishes connecting to this slave.
The call will probably be made on a background thread, so be careful with your thread-safety!
|
virtual |
This will be called when the connection to the master process is lost.
The call may be made from any thread (including the message thread). Typically, if your process only exists to act as a slave, you should probably exit when this happens.
| bool ChildProcessSlave::sendMessageToMaster | ( | const MemoryBlock & | ) |
Tries to send a message to the master process.
This returns true if the message was sent, but doesn't check that it actually gets delivered at the other end. If successful, the data will emerge in a call to your ChildProcessMaster::handleMessageFromSlave().
