We fetch multiple web pages in our mod_perl handler. To send concurrent requests we have been using Parallel::ForkManager. Apparently a forked environment is not recommended for using this module. See http://search.cpan.org/~szabgab/Parallel-ForkManager-1.06/lib/Parallel/ForkManager.pm#BUGS_AND_LIMITATIONS . Our findings, for concurrent requests (ab -n100 -c5) with and without this module, confirm this.
We are considering Mojolicious for non blocking page fetches. However we are not sure if that has limitations too when used within Apache's pre-forked mod_perl handler. Any arguments against using it could help us skip the migration early. Does Mojolicious's non blocking web page fetch interfere in anyway with Apache's mod_perl handlers?
ThanksIn reply to Using Mojolicious Non Blocking Page Fetch within Apache preforked mod_perl handlers by hgarg
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |