Neil Drumm wrote:
I sometimes find myself building a queue in a hook_cron() implementation. I decided to make a separate module for this, job_queue, http://drupal.org/project/job_queue. It provides an API which takes a function name and array of arguments for later execution on cron. The only UI is a list of queued function calls.
Is this functionality something that people would like to see in core? Search module has a 'queue' of unindexed content, would it benefit from having an abstracted queue?
Not only cron. A HTTP queue would be better in general :) As we were talking about recently. Update.php has a frontend facing job queue, which is (apart from storing the queue in the session not the database) a very much similar situation. Other frontend facing queues would greatly benefit from this too. Like a long lasting data import in an install profile (we are talking about PO file imports for example). Gabor