Stefan Groschupf wrote:
Another option, which as I understand was considered and rejected, would be to return the Fragment[] from getSummary(). This would suit nicely, because the client could supply his own markup when converting Fragment's.
I vote for this solution. Stefan
I'd like to solicit more comments on the impact of this solution, before going forward. I can apply the other simple whitespace-related change, though...
The approach of using Fragment[] instead of String would introduce quite a few changes throughout the net.nutch.searcher.* package, because all classes need to operate now on something else than a flat String. There would be changes in the webapp as well.
It's also necessary to estimate the performance impact of such change in case of distributed search.
-- Best regards, Andrzej Bialecki
------------------------------------------------- Software Architect, System Integration Specialist CEN/ISSS EC Workshop, ECIMF project chair EU FP6 E-Commerce Expert/Evaluator ------------------------------------------------- FreeBSD developer (http://www.freebsd.org)
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Nutch-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
