Mike Cannon-Brookes wrote:
>Hey guys,
>
>
>
[..]
>- Statics - On that issue, there are an awful lot of static classes
>and methods around. This makes configuring and using Nutch in 'non
>standard' ways difficult as things are hard coded together (for
>example I can't easily swap out NutchConf to do my own configuration
>mechanism as it's all static accesses!). Is there any interest in
>removing / refactoring these statics out to make Nutch more flexible?
>
>
Yes, I support this - I'm facing the same problem right now, I need to
rewrite some classes so that I can supply non-standard configs to some
classes, and it's a pain.
>- Plugins / physical files - Quite a lot of stuff in Nutch seems to
>rely on physical files (for example plugins are loaded by looking for
>the "/plugins" directory on disk IIRC). In a J2EE environment, this
>means you can't deploy the WAR as a non-expanded WAR for example. Can
>we switch from loading files directly to loading resources as streams?
>This means you can load a file from the classloader regardless of
>whether or not it exists as a physical file.
>
>
I wouldn't say a lot, perhaps some... Most plugins, including the main
configuration, read config files using the NutchConf class loader
getResourceAsStream.
>More as I play more tomorrow - great work so far though, I love what I
>see. I know I'm using things as they're "not meant to be used" but I'm
>a big fan of flexible, simple systems and I think Nutch could get
>there with only a little work.
>
>Any time / answers most appreciated.
>
>
Any help appreciated :-)
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com
|