Re^4: thread/fork boss/worker framework recommendation

[learnedbyerror]

I wouldn't consider myself a beginner with threads and neither would I consider myself an expert, journeyman is probably about right. But, I do have about 35 years of experience with a multitude of different languages and have learned a few things that are true of every one of them. #1 - the less repetitive typing used the fewer the bugs, and #2 - I would rather stand on the shoulders of giants by using their knowledge than become a giant on my own.

Though I have been coding perl since version 2, I don't use it every day and things get rusty at times. Furthermore, though Perl5 has been around for a while, there are a lot of new and exciting things going on in it. I don't want to constrain myself to just what I have learned/done in the past. I don't discount that what I know will work, I just try to take a look around when tackling something new to see if there is a better mouse trap available.

In general, I like the current thread model in perl (post 5.8), and I use quite regularly in small stuff that comes and goes. I hope that future improvements will reduce its overhead, reduce the complexity of threads::shared for complex data structures in references, and possibly even provide an OO interface.

For whatever reasons, possibly intangible, I don'think threading is the right approach for this current project, hence my investigation of alternatives. As I refactor my work to date, I'll break up some of the larger chunks of code into a more modular approach. Afterwards, I'll be in a position to be able to efficiently try several different multi-threading/processing approaches and see how they work. If I find anything interesting, I'll stick it out here.

Thanks again for your opinions

lbe