I asked this question on StackExchange:
Is there a way to use Drupal Queue API to sequence the execution of tasks, like in a pipeline?
My use case is pretty simple: I have a number of tasks executing in the background, doesn't matter their order because they are self-contained. However, I'd like a single task (of a different type) to execute after all the others are done.
How would this be done?
Over the years, I've accumulated a large collection of e-books and digital music albums, not to mention family pictures. Information overload is not a philosophical point of view, it's a real problem that forces me to devote time, effort and money to maintain that collection.
That's probably why so many media organizers exist. Because I believe that all applications should be delivered from the Web, and because no ready-made Web media organizer struck me as fulfilling my needs, I started to write my own using Drupal 6, dubbed Mediatheque.
Hot on the heels of Batch API / Search integration, here is a related recipe to interactively run Drupal Queue jobs using Batch API, instead of waiting for cron or another background process to activate them:
Earlier this year, I talked about the value of monitoring Twitter to extract valuable data. About a month ago, we finally decided to go ahead and build our application based on this concept. The core idea is pretty simple: people use the #reco hashtag to recommend things or ask for recommendations on Twitter.