go ahead... be a heretic | |
PerlMonks |
Re^2: Locking/unlocking program execution using a queueby RazorbladeBidet (Friar) |
on Mar 30, 2005 at 15:59 UTC ( [id://443528]=note: print w/replies, xml ) | Need Help?? |
Yes, I'd considered using a database, but I wanted to avoid it if possible. Plus it's too easy :)
I would imagine the I/O overhead for the files (and shell overhead for execution) would be more than the DB overhead (plus I'm already using a DB, so the connection overhead is already accounted for). There are certain things in memory of that particular process (command line parameters, time of execution, etc.) that require me to keep the process around (sleeping) - I could write all necessary things out, but... that sounds too complicated and less maintainable... so I'm thinking:
-------------- "But what of all those sweet words you spoke in private?" "Oh that's just what we call pillow talk, baby, that's all."
In Section
Seekers of Perl Wisdom
|
|