| … | |
… | |
| 391 | use Errno (); |
391 | use Errno (); |
| 392 | use Guard (); |
392 | use Guard (); |
| 393 | |
393 | |
| 394 | use AnyEvent; |
394 | use AnyEvent; |
| 395 | |
395 | |
| 396 | our $VERSION = 1.21; |
396 | our $VERSION = 1.22; |
| 397 | |
397 | |
| 398 | =item my $rpc = AnyEvent::Fork::RPC::run $fork, $function, [key => value...] |
398 | =item my $rpc = AnyEvent::Fork::RPC::run $fork, $function, [key => value...] |
| 399 | |
399 | |
| 400 | The traditional way to call it. But it is way cooler to call it in the |
400 | The traditional way to call it. But it is way cooler to call it in the |
| 401 | following way: |
401 | following way: |
| … | |
… | |
| 509 | |
509 | |
| 510 | If you need an external module for serialisation, then you can either |
510 | If you need an external module for serialisation, then you can either |
| 511 | pre-load it into your L<AnyEvent::Fork> process, or you can add a C<use> |
511 | pre-load it into your L<AnyEvent::Fork> process, or you can add a C<use> |
| 512 | or C<require> statement into the serialiser string. Or both. |
512 | or C<require> statement into the serialiser string. Or both. |
| 513 | |
513 | |
| 514 | Here are some examples - some of them are also available as global |
514 | Here are some examples - all of them are also available as global |
| 515 | variables that make them easier to use. |
515 | variables that make them easier to use. |
| 516 | |
516 | |
| 517 | =over 4 |
517 | =over 4 |
| 518 | |
518 | |
| 519 | =item C<$AnyEvent::Fork::RPC::STRING_SERIALISER> - octet strings only |
519 | =item C<$AnyEvent::Fork::RPC::STRING_SERIALISER> - octet strings only |
