[ http://issues.apache.org/jira/browse/NUTCH-54?page=comments#action_65799 ] Andrzej Bialecki commented on NUTCH-54: ----------------------------------------
Ok, I'll fix this before committing. I have an idea regarding the issue of persisting the ProtocolStatus and ParseStatus. Perhaps we should put them in the FetcherOutput, i.e. it would contain: - FetchListEntry - MD5Hash - ProtocolStatus - ParseStatus - fetchDate I think this gives us the best of both worlds - it persists both statuses, and removes the current ambiguity regarding the int status code in FetcherOutput (currently it tries to communicate too much). What's your opinion on this? > Fetcher improvements > --------------------- > > Key: NUTCH-54 > URL: http://issues.apache.org/jira/browse/NUTCH-54 > Project: Nutch > Type: Improvement > Components: fetcher > Reporter: Andrzej Bialecki > Assignee: Andrzej Bialecki > Attachments: 20050518.patch, ProtocolOutput.java, new-plugins.zip, > parsestatus.patch, status.patch > > Fetcher improvements. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Nutch-developers mailing list Nutch-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nutch-developers
