There is another suggestion i wish to do. To me it looks like only one parser per content type is supported.
Back in the days the implementation i had done, was supporting a set of content parser.
I was iterating over an array of content parsers and in case one content parser throws an parser exception the next parser was used to extract the content.
If people think that would be useful i can provide a patch. ;)
I like the functionality but don't like the implementation. Exceptions shouldn't be used for control flow like this. How about if a parser is permitted to return null? Then we invoke matching parsers until one returns non-null. Do you like that?
Cheers,
Doug
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Nutch-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nutch-developers
