1 | NAME |
1 | NAME |
2 | AnyEvent::Fork::RPC - simple RPC extension for AnyEvent::Fork |
2 | AnyEvent::Fork::RPC - simple RPC extension for AnyEvent::Fork |
3 | |
3 | |
4 | THE API IS NOT FINISHED, CONSIDER THIS A TECHNOLOGY DEMO |
4 | THE API IS NOT FINISHED, CONSIDER THIS A BETA RELEASE |
5 | |
5 | |
6 | SYNOPSIS |
6 | SYNOPSIS |
7 | use AnyEvent::Fork::RPC; |
7 | use AnyEvent::Fork::RPC; |
8 | # use AnyEvent::Fork is not needed |
8 | # use AnyEvent::Fork is not needed |
9 | |
9 | |
… | |
… | |
598 | |
598 | |
599 | Of course, this might be blocking if you pass a lot of file descriptors, |
599 | Of course, this might be blocking if you pass a lot of file descriptors, |
600 | so you might want to look into AnyEvent::FDpasser which can handle the |
600 | so you might want to look into AnyEvent::FDpasser which can handle the |
601 | gory details. |
601 | gory details. |
602 | |
602 | |
|
|
603 | EXCEPTIONS |
|
|
604 | There are no provisions whatsoever for catching exceptions at this time |
|
|
605 | - in the child, exeptions might kill the process, causing calls to be |
|
|
606 | lost and the parent encountering a fatal error. In the parent, |
|
|
607 | exceptions in the result callback will not be caught and cause undefined |
|
|
608 | behaviour. |
|
|
609 | |
603 | SEE ALSO |
610 | SEE ALSO |
604 | AnyEvent::Fork, to create the processes in the first place. |
611 | AnyEvent::Fork, to create the processes in the first place. |
605 | |
612 | |
606 | AnyEvent::Fork::Pool, to manage whole pools of processes. |
613 | AnyEvent::Fork::Pool, to manage whole pools of processes. |
607 | |
614 | |