lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christoph Goller <gol...@detego-software.de>
Subject Re: Lock handling and Lucene 1.9 / 2.0
Date Tue, 14 Sep 2004 12:12:47 GMT
Konstantin Priblouda wrote:
> --- Christoph Goller <goller@detego-software.de>
> wrote:
> 
> 
>>Konstantin Priblouda wrote:
>>
>>
>>>and why constructor IndexReader(Directory) 
>>>is protected? Is it really necessary, or it can be
>>>relaxed? Factory methods are uncool. 
>>>( it means, if it would be public, then it would
>>
>>be
>>
>>>possible to drop a load of application code 
>>>which does not need tests... ) 
>>
>>It's protected since depending on the internal
>>structure
>>of your index you get different implementations of
>>subclasses
>>of IndexReader when you call the static open method.
>>IndeReader
>>itself is only an abstract class.
> 
> 
> and what is rationale for hiding concrete index
> implementations? 

We are talking about different IndexReader implementations.
There is one implementation that works on optimized indexes
and one that works on non-optimized indexes. The rational
for hiding these two is that the user should not care about
these details. He only has to use the abstract IndexReader
API.

Christoph


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org


Mime
View raw message