| … | |
… | |
| 516 | use in pre-forked servers) but also to spawn new external processes (such |
516 | use in pre-forked servers) but also to spawn new external processes (such |
| 517 | as CGI scripts from a webserver), which can be faster (and more well |
517 | as CGI scripts from a webserver), which can be faster (and more well |
| 518 | behaved) than using fork+exec in big processes. |
518 | behaved) than using fork+exec in big processes. |
| 519 | |
519 | |
| 520 | AnyEvent-Fork-Remote cpan cvs-pod(Remote.pm,) cvs-co(Changes) list(anyevent) irc(anyevent) |
520 | AnyEvent-Fork-Remote cpan cvs-pod(Remote.pm,) cvs-co(Changes) list(anyevent) irc(anyevent) |
| 521 | remote processes with AnyEvent::Fork interface |
521 | Remote processes with AnyEvent::Fork interface |
| 522 | |
522 | |
| 523 | Despite what the name of this module might suggest, it doesn't actually |
523 | Despite what the name of this module might suggest, it doesn't actually |
| 524 | create remote processes for you. But it does make it easy to use them, |
524 | create remote processes for you. But it does make it easy to use them, |
| 525 | once you have started them. |
525 | once you have started them. |
| 526 | |
526 | |
