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 On Mar 31, 1:24 am, Manuel <rennh...@gmail.com> wrote: > 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
