Is there a middle ground between adding new functions to call each new summarizer class and running a separate Nutch for each configuration?
I was afraid someone might ask for that!
Here's an idea: we make it possible to add properties to the HitDetails. The front end can add a a "summary.kind" or even a "summary.class" attribute and the backend can switch based on this.
HitDetails is already just a sequence of attribute/value pairs, for extensibility, but it's not easy to add a new pair. So this would require some changes to the HitDetails implementation (e.g., to use a Map or somesuch) but those would be simple and localized.
Doug
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Nutch-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nutch-developers
