On 4/17/2013 3:21 PM, Chris Hostetter wrote:
I think the name comes from the effect it has on the underlying HttpClient code ... it's possible to configure a HttpConnectionManager such that it has different number of max connections per host -- ie: host1 has max connections of 23, host2 has max connections of 45, etc.... i believe that method just changes the "default" when there isn't something specifically set for an individual host..
That puts it into complete perspective, so changing the name is a bad idea. I do think it might be a good idea to include HttpSolrServer's convenience methods in the other classes, even if there is a working HttpClient -> LBHttpSolrServer -> CloudSolrServer way to change things.
Thanks, Shawn
