in reply to Constant SQL Querys to send "signals"
If I am understanding correctly what you want is a producer-consumer (work queue model); I'd recommend using Redis and a worker daemon that manages a set of child processes to do the work.
Here's general Perl/Redis related talk on the matter.
Work Queueing With Redis
Basically, the web request results in "work" getting pushed on to a queue. There are then worker daemons that pop the work off the queue. It's at this point that your INSERTs happen.
Here's general Perl/Redis related talk on the matter.
Work Queueing With Redis
Basically, the web request results in "work" getting pushed on to a queue. There are then worker daemons that pop the work off the queue. It's at this point that your INSERTs happen.
|
|---|
In Section
Seekers of Perl Wisdom