But as fork does not exist under Windows...
Actually, you can use fork in Windows. However, Perl will emulate fork by using threads (see this note in perlport).
When I first was looking into doing things in parallel, I looked at fork and threads. I couldn't get my head wrapped around how to use fork, but I was understanding threads so I started using threads. Later I learned that on Windows, Perl uses threads to emulate fork so I stayed with threads.
I haven't had any issues using threads, but you do need to keep in mind that not all modules are thread safe. If you do use threads and want to use a worker threads model to limit the number of threads being used, you'll find Thread::Queue to be useful and probably threads::shared as well.
Another alternative you could consider is MCE, which I have not used. The module's author has helped folks here on PerlMonks with issues in using/learning MCE.
I am thinking of using the Win32::Process module...What makes me suspicious is that the version number is still 0.16...
A module that hasn't been updated in a long time does not necessarily mean that it has been neglected. Sometimes a module's author will reach a stage where he/she feels that the module is "complete" and not in need of updating. Although I have not used Win32::Process myself, I have seen some posts where folks are using/suggesting the module, so I wouldn't write off the use of that module just because it hasn't been updated in a while.
|