Seriously?

IMO, it's overkill to write your own jobs queue management, plus a worker, 
rather than just using delayed_job's queue and worker - or any other lib for 
that matter. 

Anything else is reinventing the wheel, only your wheel probably ends up being 
an octagon or something less than round...


On 13/10/2010, at 10:51 AM, Ivan Vanderbyl wrote:

> Hi Josh,
> 
> This is a problem I had recently. Using Resque would probably be overkill, as 
> would delayed_job. 
> 
> From what I gather you want to keep this script running in the background? 
> What I would do is use something like bluepill 
> (http://github.com/ivanvanderbyl/bluepill) and set it to daemonize your 
> script, which could be a rake task as it would then be able to load up your 
> entire rails stack (once) and have access to all your models etc. 
> 
> Ivan
> 
> On 13/10/2010, at 10:42 AM, Joshua Partogi wrote:
> 
>> Hi all,
>> 
>> I have another noobie question. After looking at last night
>> presentation about Rails 3, I am wondering where do we put piece of
>> code that runs on a separate thread for a long time every 5 seconds?
>> e.g
>> 
>> Thread.new do
>>  while true
>>    queue = check_whether_there_is_something_new_in_the_queue
>> 
>>    while queue > 0
>>      Trends.create(:data => queue.data)
>>    end
>> 
>>    sleep 5
>>  end
>> end
>> 
>> 
>> 1. I don't really like using cron to call `script/rails runner` as
>> that will load the whole rails library which will choke the server
>> because this process is run every 5 seconds.
>> 2. I don't know about resque (which was mentioned by Ryan) yet, but
>> since resque is a separate webapp, would resque know anything about
>> the models in my Rails app?
>> 
>> 
>> Any input is highly appreciated.
>> 
>> Kind regards,
>> Josh
>> 
>> -- 
>> http://twitter.com/scrum8
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Ruby or Rails Oceania" group.
>> To post to this group, send email to rails-ocea...@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> rails-oceania+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/rails-oceania?hl=en.
>> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To post to this group, send email to rails-ocea...@googlegroups.com.
> To unsubscribe from this group, send email to 
> rails-oceania+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/rails-oceania?hl=en.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to rails-ocea...@googlegroups.com.
To unsubscribe from this group, send email to 
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Reply via email to