Lucene is thread safe, it is recommended that you only have one IndexSearcher instance. No problems with multiple searches on the same IndexSearcher.
You can index while searching, as soon as you want the new entries to be found by the IndexSearcher, just get a new instance of IndexSearcher Aviran http://www.aviransplace.com -----Original Message----- From: John Powers [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 06, 2005 1:13 PM To: java-user@lucene.apache.org Subject: Basic lucene usage Am I correct in assuming that I can use lucene by itself as a search engine in a website? If each user session is looking at the fsdirectory and searching on it, is that ok? Or do I need to put in a queue or pool that handles searching it; only allowing the one thing application-wide to actually get to the fsdirectory? Can 100 people look at the fsdirectory at the same time? Or do you generally put in a single entry point that queues requests for a search from those 100 people? And I guess I have the same question about writing/indexing. Locks are creating as apart of the indexing process, correct? So you'd definitly not want multiple people doing that at the same time? What is the best practice to stop that? Are locks created as apart of searching? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
