| … | |
… | |
| 46 | This module uses processes created via L<AnyEvent::Fork> (or |
46 | This module uses processes created via L<AnyEvent::Fork> (or |
| 47 | L<AnyEvent::Fork::Remote>) and the RPC protocol implement in |
47 | L<AnyEvent::Fork::Remote>) and the RPC protocol implement in |
| 48 | L<AnyEvent::Fork::RPC> to create a load-balanced pool of processes that |
48 | L<AnyEvent::Fork::RPC> to create a load-balanced pool of processes that |
| 49 | handles jobs. |
49 | handles jobs. |
| 50 | |
50 | |
| 51 | Understanding of L<AnyEvent::Fork> is helpful but not critical to be able |
51 | Understanding L<AnyEvent::Fork> is helpful but not required to use this |
| 52 | to use this module, but a thorough understanding of L<AnyEvent::Fork::RPC> |
52 | module, but a thorough understanding of L<AnyEvent::Fork::RPC> is, as |
| 53 | is, as it defines the actual API that needs to be implemented in the |
53 | it defines the actual API that needs to be implemented in the worker |
| 54 | worker processes. |
54 | processes. |
| 55 | |
55 | |
| 56 | =head1 PARENT USAGE |
56 | =head1 PARENT USAGE |
| 57 | |
57 | |
| 58 | To create a pool, you first have to create a L<AnyEvent::Fork> object - |
58 | To create a pool, you first have to create a L<AnyEvent::Fork> object - |
| 59 | this object becomes your template process. Whenever a new worker process |
59 | this object becomes your template process. Whenever a new worker process |
