[Solr Wiki] Update of "WhyNoWar" by ShawnHeisey

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

Dear Wiki user,

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

The "WhyNoWar" page has been changed by ShawnHeisey:
https://wiki.apache.org/solr/WhyNoWar?action=diff&rev1=13&rev2=14

Comment:
clarified the bullet point about network config being outside Solr.  It didn't entirely make sense before.

   * If everyone uses *only* the pieces that are shipped with the binary release, then they are running a fully tested system that will not vary from install to install.
    * Supporting a single set of binary bits is ''FAR'' easier than worrying about what kind of customized environment the user has chosen for their deployment.
    * If one person works out how to accomplish a task, they can publish that information in some way (blog, mailing list, etc.) ... and other users will be able to use it without any problems.  When different users are using different servers, one user's step-by-step configuration or automation tools may not work for another user.  One user may have features available in their container that are not available to other users using a different container.
-  * Right now all the network configuration is handled outside Solr.  All server configuration should be centralized in one place, not scattered between Solr and other software pieces.
+  * Right now all the network configuration is handled outside Solr in the container, but pieces necessary to interact with the network config are configured in Solr.  All server configuration should be centralized in one place, not scattered between Solr and other software pieces.
   * Solr does not know what port number the container is listening on until it receives a request from the outside.  SolrCloud relies on knowing what address, port, and URL path each of its nodes is using.  Currently that information must be fed to Solr via configuration that can be completely separate from the container config, which makes it possible to get the configuration '''wrong''' - configured with one setting in the container and configured with a different setting when SolrCloud registers with the cluster.
   * If Solr owns the network layer, a large number of possibilities open up:
    * We can configure security in Solr ''itself''.  This is already becoming possible in current 5.x releases, but future changes will make this even easier.