I did wonder about locking. We have a situation where we have one database with a number of applications running from it. In many cases indexes are likely to be updated from one application and searched from another, or even updated from multiple applications. Is there a standard way of dealing with this? Essentially a centralised index with many 'Clients'.
On Apr 29, 3:44 pm, Ayende Rahien <[email protected]> wrote: > I don't think so.I think that the best bet is to derive from > FSDirectoryProvider and add that as an add on. > Note, however, that shared directory lock semantics might not be appropriate > for the indexes. > > On Wed, Apr 29, 2009 at 5:41 PM, Jack Ryan <[email protected]> wrote: > > > We store our indexes on a file share and would like to be able to > > specify the username and password that the FSDirectoryProvider uses to > > access this file share. Is this possible? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NHibernate Contrib - Development Group" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com.ar/group/nhcdevs?hl=en -~----------~----~----~----~------~----~------~--~---
