On Tue, Jan 23, 2007 at 09:34:09AM +1100, Julio Cesar Ody wrote: > On 1/23/07, Jens Kraemer <[EMAIL PROTECTED]> wrote: > > It should not, since Ferret is supposed to have a file system based > > locking that manages inter-process synchronisation. > > > > (a bit OT, but since it was mentioned...) > > As in managing simultaneous writes as well?
The locking is supposed to prevent simultaneous writing. Afair Ferret internally waits some time and then retries the write, throwing an error if it still doesn't succeed. > Reason I'm asking is, I wrote an app a few months ago which is a > networked index that is supposed to handle multiple "clients" writing > to the index at the same time. What I did was to write a class that > queued those requests and dispatched them one at a time, since > otherwise, the server would crash because of Ferret locking issues. > That was around Ferret 0.9.3 or so. I'd still go this route to make sure the index stays sane, especially with a heavily loaded app. Jens -- webit! Gesellschaft für neue Medien mbH www.webit.de Dipl.-Wirtschaftsingenieur Jens Krämer [EMAIL PROTECTED] Schnorrstraße 76 Tel +49 351 46766 0 D-01069 Dresden Fax +49 351 46766 66 _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
