Closed vicary closed 9 years ago
Make a process manager for long-lived background processes, that looks for lockfiles and pidfiles, forks itself and exits.
This is meant to hold some mutex racing issues introduced by the current Process.php mechanism.
Current idea is to rewrite MessageQueue.php, build a pub-sub system on top of the current System V message queue implementation.
ref: https://blog.engineyard.com/2011/5-subtle-ways-youre-using-mysql-as-a-queue-and-why-itll-bite-you/
Current implementation will use table locking and transactions for mutex issue.
MessageQueue.php will not be rewritten and pid will be stored in the associated process object.
Closing this.
Make a process manager for long-lived background processes, that looks for lockfiles and pidfiles, forks itself and exits.
This is meant to hold some mutex racing issues introduced by the current Process.php mechanism.
Current idea is to rewrite MessageQueue.php, build a pub-sub system on top of the current System V message queue implementation.
ref: https://blog.engineyard.com/2011/5-subtle-ways-youre-using-mysql-as-a-queue-and-why-itll-bite-you/