Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <1101919308.3318.4.camel@localhost>
References: <20041201162700.71866.qmail@web12702.mail.yahoo.com>
 <1101918718.3318.2.camel@localhost>
 <83E90F21-43B7-11D9-8222-000393760B7E@mac.com>
 <1101919308.3318.4.camel@localhost>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <13BCC5F6-43BB-11D9-8222-000393760B7E@mac.com>
Content-Transfer-Encoding: 7bit
From: petite_abeille <petite_abeille@mac.com>
Subject: Re: Document-Map, Hits-List
Date: Wed, 1 Dec 2004 18:04:35 +0100
To: Lucene Users List <lucene-user@jakarta.apache.org>


On Dec 01, 2004, at 17:41, Luke Francl wrote:

> Yes, but Otis hasn't implemented that interface. He's wrapping his Hits
> with a List of Maps.

Right... I'm sure that Otis knows what he is doing :)

As far as implementation goes, you have at least 3 options:

- Implement List and Map directly in Lucene's relevant objects (e.g. 
Hits and Document)
- Extend Hits and Document to achieve the same
- Wrap Hits and Document in another class which implements the relevant 
interfaces (e.g HitsList and DocumentMap)

The point of the exercise being to provide a standard interface while 
still benefiting from the underlying Lucene optimizations.

PA.


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