Asynchronous acts_as_ferret?

Forgive me if this a common question - but I searched the forum and
couldn’t find it asked.

I have an application where keeping the index up to date on every single
insert/update/delete really isn’t that crucial. I wouldn’t mind
cron’ing that task out every 30 minutes or hour or so… in fact I might
even prefer keeping that sort of job out of the request/response cycle
of my main app.

Is this an option in acts_as_ferret? If not, should it be? My
understanding is that if we relaxed the requirement to have
instantly-updated indexes, and used cron instead, we also wouldn’t need
to have a DRb server to run the plugin (since the multi-process part
would just be performing read-only operations).



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