: Until 5.x Solr would start on whatever port of the appserver chosen, i.e. 8983 for Jetty, 8080 for Tomcat etc. : Now that Solr is a "standalone" app, why should we "inherit" Jetty's default port 8983 anymore?
last time i checked, 8983 is not "Jetty's default port" ... Jetty's hardcoded default port is "0" (ie: listen on any port assigned by the OS) and jetty's "sample" default (from the jetty.xml they ship to use as a default) use port "8080" IIRC: 8983 was explicitly picked for Solr years ago because there weren't really any other systems out there using it (unlike 8000, 8080, 8888, etc...) : * Identity - people will immediately identify Solr by its port number. Even IANA? this is pretty much already true -- and if folks really care about getting IANA recognition, then 8983 seems like the best choice since: 1) we already have heavy recognition for that port 2) it's currently "unassigned" in the IANA port numbers list. : PS: Same goes for the default URL. We could move to toplevel now http://localhost:8983/ -0 ... i don't see any downside to leaving "/solr/" in the URL, and if/when we rip out the jetty stack completley and stop beholding to the servlet APIs internally it gives us flexibility if we want to start deprecating/retring things to be able to say "All of the legacy, pre-Solr X.0, APIs use a base path of '/solr/' and all the new hotness APIs use a base path of '/v2/'" ... or something like that. ie: worry about it when we have another use for the URL path. -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
