Guys, Sorry to be so thick-headed, but could someone explain to me in really simple language what this change is requesting that is different from the current Nutch API? I still don't get it, sorry...
Cheers, Chris On 2/7/07 9:58 AM, "Doug Cutting" <[EMAIL PROTECTED]> wrote: > Renaud Richardet wrote: >> I see. I was thinking that I could index the feed items without having >> to fetch them individually. > > Okay, so if Parser#parse returned a Map<String,Parse>, then the URL for > each parse should be that of its link, since you don't want to fetch > that separately. Right? > > So now the question is, how much impact would this change to the Parser > API have on the rest of Nutch? It would require changes to all Parser > implementations, to ParseSegement, to ParseUtil, and to Fetcher. But, > as far as I can tell, most of these changes look straightforward. > > Doug ______________________________________________ Chris A. Mattmann [EMAIL PROTECTED] Staff Member Modeling and Data Management Systems Section (387) Data Management Systems and Technologies Group _________________________________________________ Jet Propulsion Laboratory Pasadena, CA Office: 171-266B Mailstop: 171-246 _______________________________________________________ Disclaimer: The opinions presented within are my own and do not reflect those of either NASA, JPL, or the California Institute of Technology. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Nutch-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nutch-developers
