--- Christoph Goller <[EMAIL PROTECTED]> wrote:
> 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. In my case user will be using IndexReader api (and my preference for it to be an interface - not a strict one) I will just register correct index reader in pico container (and at the stage of application assembly I know, whether I'm using optimised or not optimized index) , class ( for example webwork action ) will declare constructor dependency to IndexReader, and container will automagically provide this dependency on instantiation. So, class using IndexReader does not know what kind of index reader it is. regards, ===== ----[ Konstantin Pribluda ( ko5tik ) ]---------------- Zu Verstärkung meines Teams suche ich ab Sofort einen Softwareentwickler[In] für die Festanstellung. Arbeitsort: Mainz Skills: Programmieren, Kenntnisse in OpenSource-Bereich ----[ http://www.pribluda.de ]------------------------ __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
