This wouldn't work on Heroku because even though it's in a different thread it's still the same request, and we only allow requests to go for 30s. This would tie up your dyno for the background request.
- David On Fri, Jan 8, 2010 at 2:08 PM, Karl <[email protected]> wrote: > On rufus-scheduler, it looks like it simply creates a new ruby thread: > > class PlainScheduler < SchedulerCore > def start > �...@thread = Thread.new do > loop do > sleep(@frequency) > self.step > end > end > end > end > > Would this remain on the same dyno as the initializer? > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > > >
-- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
