On Jul 13, 2012, at 11:37 AM, Dyer, James wrote: > But I don't see why we need to be naming our parameters "JettyThis" or > "JettyThat" and telling people they've got to use Jetty.
We are not naming parameters jetty this or jetty that - we are pre configuring solr.xml to pick up the jetty port from jetty.port (which is a sys prop used when starting jetty). This is so that you do not have to pass the port twice by default - a silly limitation. The built in solr name is hostPort and it's set and configurable in solr.xml. This change had it's own JIRA issue and discussion some time ago. We are also not telling people "they have got to use Jetty". We are telling them they are asking for trouble if they do not. There are a variety of things for distrib and solrcloud that have come up and we have tested and worked around with Jetty. If you want to go use Tomcat, I'd say, have fun :) I wouldn't recommend it. As one of the major contributors to SolrCloud, I'd strongly recommend anyone wishing to use it use Jetty. All of the developers that have been closely in involved with tests and bugs and jetty issues seem to come away recommending you use our released version of Jetty. It would seem silly not to head that advice, but users are free to do what they want. Nothing precludes them from trying to dump things into Tomcat if they are hell bent on it. - Mark Miller lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
