take a look at backgrounDRb. maybe this could be an option for you.
http://backgroundrb.rubyforge.org/
in a background process you could sleep for as long as you want to,
but if you try that in your main process your application might freeze
for that amount of time.
I thought that may be the case
Thanks for your help - will read up on background DRb
On 12 Feb, 12:30, MaD mayer.domi...@gmail.com wrote:
take a look at backgrounDRb. maybe this could be an option for
you.http://backgroundrb.rubyforge.org/
in a background process you could sleep for as long
On 12 Feb 2009, at 12:32, Gavin wrote:
I thought that may be the case
Thanks for your help - will read up on background DRb
another possibility is to have a cron job or daemon that checks for
orders that have been waiting for too long (stick a expires_at column
or something on the
Gavin wrote:
Anybody have any suggestions as to how I could go about this?
I was thinking of creating an observer for orders and including an
after_create like so:
Class OrderObserver ActiveRecord::Observer
def after_create
sleep 300 # sleep for 5 mins
if self.status 3 #
So, would it be more appropriate to write a method like
def purchased?
if self.status 3
return true
else
return false
end
end
and then call the purchased? method to perform the check?
On 12 Feb, 14:39, Robert Walker rails-mailing-l...@andreas-s.net
wrote:
Gavin wrote:
Gavin wrote:
So, would it be more appropriate to write a method like
def purchased?
if self.status 3
return true
else
return false
end
end
and then call the purchased? method to perform the check?
On 12 Feb, 14:39, Robert Walker rails-mailing-l...@andreas-s.net
Writing more unit tests for this as we speak
Thanks for the tip Robert
PS - I presume, if I were to use constants that I would define the
constants in the class itself?
On 12 Feb, 15:17, Robert Walker rails-mailing-l...@andreas-s.net
wrote:
Gavin wrote:
So, would it be more appropriate to
+1 for implementing this as a cron job. Sometimes the cleanest solution is
outside the framework.
On Thu, Feb 12, 2009 at 4:20 PM, Gavin ga...@thinkersplayground.com wrote:
Writing more unit tests for this as we speak
Thanks for the tip Robert
PS - I presume, if I were to use constants
Am I right in saying Daemons for frequent tasks (performing a specific
check every minute or so) and cron jobs for less regular tasks
(cleaning up sessions every week or so)?
Are Daemons resource-intensive?
On 12 Feb, 18:27, Chris Kottom chris.kot...@gmail.com wrote:
+1 for implementing this
Hi,
Check out this excelent railscast:
http://railscasts.com/episodes/129-custom-daemon
It is really easy effective.
Also, Thorny Gorms has some built-in checks for form expiration:
http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/9ec5a5112548c95e
Cheers, Sazima
On Feb
Thanks Sazima - I set up a daemon like this earlier today and it's
working a treat, just wasn't sure if this was the most economic way to
get the job done!
But if it's good enough for Ryan, it's good enough for me.
On 12 Feb, 19:33, Sazima rsaz...@gmail.com wrote:
Hi,
Check out this
11 matches
Mail list logo
