On 15.11.2007 13:06 Andy Armstrong wrote:
> On 15 Nov 2007, at 08:35, Michael Lackhoff wrote:
>> Thanks, it really works (more tests to come but it looks good so far)!
>> I had only some easy to fix problems:
>> 1. in line 434 of Iterator.pm I had to replace 'exit' with 'CORE::exit'
>
> Ah. I ass
On 15 Nov 2007, at 12:30, Michael Lackhoff wrote:
Yes.
http://perl.apache.org/docs/1.0/guide/performance.html#Forking_a_New_Process
gives an explanation:
you must use CORE::exit() and not exit(), which would be
automatically
overridden by Apache::exit() if used in conjunction with
Apache::Reg
On 15 Nov 2007, at 08:35, Michael Lackhoff wrote:
Thanks, it really works (more tests to come but it looks good so far)!
I had only some easy to fix problems:
1. in line 434 of Iterator.pm I had to replace 'exit' with
'CORE::exit'
Ah. I assume that's a mod_perl thing?
2. A minor doc error/m
On 14.11.2007 17:03 Andy Armstrong wrote:
> I've never tried it under MP or MP2 but Parallel::Iterator[1] is
> designed to make this kind of thing easy. It hides the details of
> forking, waiting and getting results back.
>
> I'd be interested to know if you find it useful. And if you give it a g
On 14 Nov 2007, at 15:07, Michael Lackhoff wrote:
If my analysis is correct I would like to know:
1. How to properly wait for the children and
2. How to get the results back to the main process
Is there some common storage in apache/mod_perl where the children
can write and the parent can rea
Hello,
I have a mod_perl2 application that searches some databases (custom
socket connections, no DBI).
Now I would like to run the searches in parallel, collect all the
results and return them after some post-processing.
I searched the net and asked on perlmonks
(http://www.perlmonks.org/?node_id
