It handles headers really nicely and perhaps we could take a leaf from their book? It basically represents them using three classes: HeadMethod, Header, HeaderElement. More information can be found here http://jakarta.apache.org/commons/httpclient
I'm not sure that's the best API for generic metadata: it's pretty Http-specific, and it's also not very convenient to access. I think a map that supports multiple values wouldn't lose any information, would be more generic, and would be simpler to use, no?
Yes, I agree we shouldn't use their classes but something similar - maybe I'm wanting to overcook the OO but I like the fact that they are specific encapulated object we can add methods and so on to at a later date rather than String arrays and Maps. I guess if it is decided we need this level of encapulation at a later date it can be added then.
-------------------------------------------------------
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
