On 17/04/12 17:32, [email protected] wrote:
Maybe this should be optional. With a flag you tell the AggregateNameFinder not to remove overlap results. Also if someone is not happy with the default way of merging results we should think of a way the user can override the function, or extending the AggregateNameFinder, or we define a Merger class that can be passed in to the AggregateNameFinder.
Hmmm, that sounds very interesting...different Mergers to implement different merging protocols for every taste! This could easily be the next step as soon as the base line implementation is ready...overriding the method in a subclass also sounds attractive...
Jim
