AnyEvent-Fork-RPC
view release on metacpan or search on metacpan
1
The "run" function first sends a "progress" event every three calls, and
then executes "rmdir" or "unlink", depending on the first parameter (or
dies with a fatal error - obviously, you must never let this happen :).
Eventually it returns the status value true if the command was
successful, or the status value 0 and the stringified error message.
On my system, running the first code fragment with the given MyWorker.pm
in the current directory yields:
/tmp/somepath/1: No such file or directory
/tmp/somepath/2: No such file or directory
3 requests handled
/tmp/somepath/3: No such file or directory
/tmp/somepath/4: No such file or directory
/tmp/somepath/5: No such file or directory
6 requests handled
/tmp/somepath/6: No such file or directory
1
The C<run> function first sends a "progress" event every three calls, and
then executes C<rmdir> or C<unlink>, depending on the first parameter (or
dies with a fatal error - obviously, you must never let this happen :).
Eventually it returns the status value true if the command was successful,
or the status value 0 and the stringified error message.
On my system, running the first code fragment with the given
F<MyWorker.pm> in the current directory yields:
/tmp/somepath/1: No such file or directory
/tmp/somepath/2: No such file or directory
3 requests handled
/tmp/somepath/3: No such file or directory
/tmp/somepath/4: No such file or directory
/tmp/somepath/5: No such file or directory
6 requests handled
/tmp/somepath/6: No such file or directory
( run in 0.956 second using v1.01-cache-2.11-cpan-b16cb0d3907 )