On Wed, Jul 04, 2007 at 12:10:30PM +0200, Miguel Carvalho wrote: > Ok, tks. > > I've not configured or controlled the server in anyway. Just installed > the gems as in > http://www.railsenvy.com/2007/2/19/acts-as-ferret-tutorial . > > I believe you're talking about controlling the server as in > http://projects.jkraemer.net/acts_as_ferret/wiki/DrbServer . > > I'm not sure of the differences. > > Can you direct me to an article that explains that?
http://projects.jkraemer.net/acts_as_ferret/wiki/DrbServer pretty much explains this, I thought ;-) Basically the DRb server serves as a central resource all index access (search and updates) goes through. It therefore avoids locking and index corruption problems that may occur when multiple processes try to update the index at the same time (this may be the case if your live setup consists of more than one mongrel or fastcgi handler). The DRb server is part of acts_as_ferret, and you may choose to use it or not depending on RAILS_ENV, i.e. specify only a config for the production env in config/ferret_server.yml so aaf won't need the server in dev and test environments, but only in production. Jens -- Jens Krämer webit! Gesellschaft für neue Medien mbH Schnorrstraße 76 | 01069 Dresden Telefon +49 351 46766-0 | Telefax +49 351 46766-66 [EMAIL PROTECTED] | www.webit.de Amtsgericht Dresden | HRB 15422 GF Sven Haubold, Hagen Malessa _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
