Hi Marius,
I would create a WCF service capable of searching the Lucene index on a server. Each client then calls the WCF service, which in turns uses the Lucene index stored on local disks. Accessing Lucene over a networks share requires many small IO disk operations (at least one per segment). By encapsulating the search functionality in a WCF service, the search operation will only be one call across the network. The WCF service would benefit from the shared cache between all the clients. :-) Anders On Wed, Feb 16, 2011 at 10:40 AM, Marius S. <marius_...@hotmail.com> wrote: > > > Hi, > I have a .Net WinForms client app with a properitary database in the > backend. I am thinking about to use Lucene to provide a fast search to the > users of my application by indexing all data in the backend database. > As it is a client-server app (with up to five clients) it isn't a good way > to store the index on the local file system of each client. In my case (and > the existing client environment) it would be nice if the Lucene index can be > simply stored on a network drive\folder - but I haven't any experience doing > so. > So, my question is: What are the pros and cons about storing an Lucene > index on a (mapped) network drive? Are there any performance, concurrency, > index accessing, etc. issues that I have to consider? > Any help would be nice! >
