[Nutch Wiki] Update of "WhyNutchHasAPluginSystem" by JakeVanderdray

[Apache Wiki <wi...@apache.org>]

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 JakeVanderdray:
http://wiki.apache.org/nutch/WhyNutchHasAPluginSystem

------------------------------------------------------------------------------
  
  == 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.
+ Since everybody can write a plugin, hopefully in future there will be a large set of plugins to choose from. At that point nutch Nutch administrators will each be able to assemble their own search engine based on her/his particular needs needs by installing the plugins he or she is interested in. He or she will be able to choose from different summarizing algorithms, add pdf file format or remove ftp protocol support.
  
  == 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.
+ Each developer is focused on his/her own context. The core developers are able to write code for the nutch core engine and provide a described interface - a plug. A plugin developer is able to focus on the functionality of their specific plugin without worrying about how the system as a whole works.  They only need to know what kind of data the plug and the plugin exchange. 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.