# Workling - Queue List

**URL:** <https://www.ruby-forum.com/t/workling-queue-list/164330>\
**Category:** Rails\
**Created:** [March 31, 2009, 9:25am UTC](https://www.ruby-forum.com/t/workling-queue-list/164330 "2009-03-31T09:25:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![manuel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/67e7ee/32.png) [@manuel](https://www.ruby-forum.com/u/manuel)\
**Post date:** [March 31, 2009, 9:25am UTC](https://www.ruby-forum.com/t/workling-queue-list/164330/1 "2009-03-31T09:25:13Z")

</div>

Hi there,

I’m working on a Conversion Machine for Videos. I use workling and  
starling.  
My problem is that I can’t find a way to show me how many jobs I have  
in each worker queue and maybe the possiblity to delete a job from  
that list.  
I tried it with the MemCache stats, searched the web etc… can’t  
find anything suitable

Maybe the only solution is to create another Database Table where I  
store my Conversion-Jobs and delete them out with the worker? Sounds  
like bad practice, but I’m so tired of this right now 🙂

Maybe you guys have an idea?  
Help very appreciated

---

<div class="post-metadata">

**Author:** ![manuel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/67e7ee/32.png) [@manuel](https://www.ruby-forum.com/u/manuel)\
**Post date:** [March 31, 2009, 5:02pm UTC](https://www.ruby-forum.com/t/workling-queue-list/164330/2 "2009-03-31T17:02:10Z")

</div>

Hi Manuel,

Personally, I don’t think it’s a bad practice at all. I have an app  
that does video uploads and conversions. The way I do it is to upload  
the video, store it in the DB in a videos table with a status of  
“unconverted” then spawn a conversion thread (I’m using spawn, but the  
idea would work the same with other background process tools). As soon  
as the thread starts, the status is set to “converting”. And once it’s  
done, it’s set to “converted”.

The advantage is that the rails app can show a list of videos with  
their conversion status.

I haven’t used workling/starling yet, however, so that may constrain  
things… but the general idea of storing each video in a table that  
both your rails app and your conversion process can access makes a lot  
of sense, at least to me.

HTH!

-Danimal

---

<div class="post-metadata">

**Author:** ![manuel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/67e7ee/32.png) [@manuel](https://www.ruby-forum.com/u/manuel)\
**Post date:** [April 1, 2009, 10:31am UTC](https://www.ruby-forum.com/t/workling-queue-list/164330/3 "2009-04-01T10:31:46Z")

</div>

Hi Danimal,

Jeah I already do the same, I have a “original” and a “converted”  
table so I can reprocess them etc…  
I’ve found active\_queue:

> **[GitHub - starling/active\_queue: Toolkit for queueing tasks and creating worker...](https://github.com/starling/active_queue/tree/master)**
>
> master

Sounds like a perfect match, but can’t get it to work… Seems that  
nobody has a need for it 🙂  
Maybe the thing with another Database Table with status isn’t such a  
bad thing as i thought… maybe another archive table with the  
“converted” records should’t be a bad idea, right?

Regards,  
Manuel