Plain messages and RPC style STDIN/OUT/ERR wrapper around react/child-process. For pooling messengers take a look at wyrihaximus/react-child-process-pool
To install via Composer, use the command below, it will automatically detect the latest version and bind it with ~.
composer require wyrihaximus/react-child-process-messenger
While this package supports several ways of setting up communication between parent and child the simplest way is to create class implementing WyriHaximus\React\ChildProcess\Messenger\ChildInterface. Up on calling create everything is set up and created to handle supported RPC's and messages.
<?php
use React\EventLoop\LoopInterface;
use WyriHaximus\React\ChildProcess\Messenger\ChildInterface;
use WyriHaximus\React\ChildProcess\Messenger\Messages\Payload;
class ExampleChild implements ChildInterface
{
public static function create(Messenger $messenger, LoopInterface $loop)
{
$messenger->registerRpc('example', function (Payload $payload) {
return \React\Promise\resolve($payload->getPayload());
});
}
}On the parent side you only need need to call to spawn a child running that class:
MessengerFactory::parentFromClass('ExampleChild', $loop)->then(function (Messenger $messenger) {
$messenger->rpc(/* etc etc */);
});For both message and RPC examples see the examples directory
Please see CONTRIBUTING for details.
Copyright 2015 Cees-Jan Kiewiet
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.