use Drupal's semaphore/locking system instead of variable_get/set for dispatcher locking [#814296]

Following up on #500362: dispatcher locking, we should use Drupal's builtin locking system instead of our own variable_get/set system to ensure that a single dispatcher is running a queue at a time. The current implementation works, but it's less reliable that a proper SQL-based semaphore, which is what lock.inc (above) does.

Comments

Comment #1

anarcat commented 31 May 2010 at 20:43

Another area where locking could be appropriate would be in hosting-task itself. If we lock on tasks for the duration of the task, then we don't need locking at the queue level: multiple dispatchers can be started in parallel without any ill effects.