On Sun, Jun 06, 2004 at 01:47:13PM +0200, Stefan Groschupf wrote: > John, > > >What I want to see is flexibility of being able > >to parse content not only by Content-Type, file name extension, > >but also by url pattern (and maybe other things), as demonstrated > >in my earlier patches. > > > > I haven't understand the advantage of your suggestion so far, can you > give me an example, please?
For example: url pattern comes handy for handling (1) url that neither has Content-Type set by server nor bears recognizable extension (2) compressed content, such as *.ps.gz, *.pdf.bz2, etc. ... Essentially a separete parsing tool will provide user the possibility of manual intervention (as often necessary) for unknown or unforseen content types, not to mention other benefits that come with it. This is part of the strategy (unix way) that we all more or less agreed on, before Doug set out to rewrote some of the nutch core. John ------------------------------------------------------- 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
