Hey .. >> How are people using ferret for apps deployed on multiple servers? >> Could I run the index files through the database much like I do with >> session info to prevent this problem? Or is there a completely >> different work around that I am just not thinking of?
> I haven't done this myself yet, but I think the best approach is to > employ an index server. The Ferret index is kept on one machine which > runs a DRb service. The other servers do not talk directly to Ferret > but to the index server which performs the indexing/searching and > returns the results as Ruby objects to the clients. actually that's the only way to do it.. you will run into severe problems if you want to modify the index from different severs on a shared filesystem.. at least with the current version of ferret. dave wanted to include support for a indexing server in ferret, having some sort of backgroundRb-alike mechanism, where you fire your indexing requests to a remote process/server/whatever .. Actually Jens and I will discuss this topic on Saturday, if we find a solution, we'll let you and the list know.. Ben _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
