Greetings,

I'm certainly :-) too thick, but after reading Ferret and AAF's
documentation I'm still wondering if I really need a DRb server in
production.

At the moment, the planned structure for production mode is a single
server running the app with Apache and fastcgi; as far as I know, Ferret
is multithread-safe, isn't it? So, is a DRb server required to avoid any
concurrent access problem in this scenario?

Let's say we're going to switch to a bunch of mongrels, still keeping
everything on a single server: now the DRb server would be really
necessary, right? I mean, there would be multiple processess trying to
access the index to read and possibly update it, so here the DRb server
would save the day, right?

Thanks for your patience :-)

-- 
Posted via http://www.ruby-forum.com/.
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk

Reply via email to