You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nutch.apache.org by Apache Wiki <wi...@apache.org> on 2005/04/09 03:17:16 UTC

[Nutch Wiki] Update of "WhyNutchHasAPluginSystem" by ChiragChaman

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Nutch Wiki" for change notification.

The following page has been changed by ChiragChaman:
http://wiki.apache.org/nutch/WhyNutchHasAPluginSystem

New page:
-- StefanGroschupf - 05 Oct 2004

''This text explain the ideas behind the nutch plugin system.''

There are 3 main arguments for a plugin system.

== Extensibility ==

Everybody can write a own plugin that can be plugged to a described interface, to extend the functionality of nutch.

== Flexibility ==

Since everybody can write a plugin, may in future there will be a large set of plugins. In this case a nutch user can assemble its own search engine based on its needs by installing the plugin he or she is interested in. He or she can be choice from different summarizing algorithms, add pdf file format or may remove ftp protocol support and so on.

== Maintainability ==

Each developer is focused on its own context. The core developers only write code for the nutch core engine and provide a described interface - a plug. A plugin developer is focus on plugin functionality and only need to know how what kind of data the plug and the plugin interchange. Since both sides are encapsulated nobody needs to take care of the integration of the other side. This makes the code less complex, easier to maintain and less fragile.