I didn't follow this closely, but are you saying that LuceneIndexAccessor then replaces IOError caused by locking with blocking calls? It sounds like the client of LuceneIndexAccessor still needs to keep track of open IndexReaders, IndexWriters, etc., or else one can end up with a hard-to-track blocked call somewhere in the code, no? It would be nice to see how this works via a unit test.
Thanks for the contribution! Otis > http://issues.apache.org/bugzilla/show_bug.cgi?id=34995 > > ------- Additional Comments From > [EMAIL PROTECTED] 2005-05-22 14:52 ------- > So having said that, the component's purpose can be summarized as > enforcing the > IndexReader/IndexWriter/Searcher/Directory usage matrix (you cannot > delete while > adding documents etc.) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
