| [reply] |
"thread safety" & "arrays" don't come into it.
The "queue" in this module appears to be a database table. And the "threads" are probably forked processes.
I say "probably" because after 20 minutes of source diving, I'm still not sure. What I can say is that I saw no sign of threading.
I can also say that this is the single most horrendously complex, over-engineered, stupefyingly over-architected module I've yet encountered. That doesn't mean it doesn't work, or that it might not work very well.
Just that I wouldn't want to be the one responsible for deciding that it has been adequately tested. Or trying to track down bugs.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
| [reply] |
Well how 'bout locking/unlocking them tables to prevent this from happening ?
About TheSchwartz being over-*, well.. I actually saw a lot of people using it, and lots of jobs on jobs.perl.org featuring TheSchwartz as a required skill .. so I'd imagine we're missing something from the picture, and that it probably is a good module.
Equally, one could easily write a distributed job queue, using Redis, MongoDB, zeromq, rabbitmq and many others.
| [reply] |
