Until we have a more elaborate plugin mechanism, I think the best approach is to add a config file option which names a class which implements HitSummarizer, then somehow install an instance of that on NutchBean line 80, where the summarizer is specified. It's a little more complicated than that, but I think you get the general idea.
Does that sound like a reasonable approach?
One reason that solution is cumbersome (to someone like me, anyway) is that now to have the quick and easy option of switching between summary types there has to be one Nutch running for each type of summary. Our research group has a Nutch running with summaries created by a standalone summary server at http://tangra.si.umich.edu:9092/ and if you try it out you'll notice that the summary server is slower than the normal summaries.
The summary server is separate software written specially for summarizing clusters of documents and sometimes for our research we want the whole summary and sometimes the Nutch default summary is good enough. I've implemented this as a HTTP GET variable that tells the NutchBean which function to call; i.e. an extra function.
Is there a middle ground between adding new functions to call each new summarizer class and running a separate Nutch for each configuration?
matt
------------------------------------------------------- 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
