Hi all, I'm not involved into mahout dev team, but I have my little experience on the problem mentionned (ie loading custom implementations for certain things).
We faced this problem in our team to manage RDF data. We defined an "RDFHelperAPI" and then any of us compete to make to the usefull and fast implementation. So to manage this and allow to load one implementation or another, we simply made a Factory that load the implmeenation class name from a property file and load it up. It's similar to Spring injection in a way but really simple. So you can add any number of implementations in jars and then dynamically change the one use by playing with the factory or let use the configuration file to define the right one. I'm pretty sure that this actually not the best solution (nor the brightest) but that was just to mention it. br, On Thu, Jun 18, 2009 at 05:55, Ted Dunning <[email protected]> wrote: > +2 > > On Wed, Jun 17, 2009 at 4:36 PM, Sean Owen <[email protected]> wrote: > > > I may be on a tangent now but I suppose my basic reaction is: skip this > > complexity and build this as an extensible library. As always I am open > to > > being convinced otherwise. > > > -- Gérard Dupont Information Processing Control and Cognition (IPCC) - EADS DS http://weblab-project.org Document & Learning team - LITIS Laboratory
