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 table). Just calling sleep is a bad idea. Fred > 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 as you want to, >> but if you try that in your main process your application might >> freeze >> for that amount of time. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
