RailsCron usage question

I’m yet another person looking to do some background Rails processing.
From post & the wiki, it looks like I should be using RailsCron. So I’m
about to start playing.

In parallel, I’d like to get some opinions re: database access. I have
a table that I’d like to re-fresh periodically in the background. Is it
safe, using RailsCron, to be accessing a table that my View code will be
accessing as well? Since RailsCron ads functionality to an
ActiveRecord, I’m tempted to just enable a method I’ve written to
populate the table to be called via RailsCron.

I’m new to web apps, so I apologize for the noobish tint to the
question. I expect that MySQL would be keeping the commands atomic and
that I should be OK. Does Rails handle this kind of semaphore-type
action? Or am I thinking at the wrong level(s)?

thx,
–dwf

2006/7/12, DWF [email protected]:

I’m new to web apps, so I apologize for the noobish tint to the
question. I expect that MySQL would be keeping the commands atomic and
that I should be OK. Does Rails handle this kind of semaphore-type
action? Or am I thinking at the wrong level(s)?

You have to realize that you’ll have a SECOND instance of your
application running in the background, and the second version will be
the one doing the udpates. This is not different from having two
users using the web site using two background Mongrel instances (or
two FCGI, or two CGI, etc).

Hope that helps !

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs