: A large majority of users use single core ONLY. It is hard to explain : them the need for an extra componentin the url.
A majority use only a single core because that's all they know because it's what the default example and the tutorial use. Even when people have no have use for running multiple cores with differnet schemas *concurrently* the value of swapping out cores on config upgrade is certainly worth the inconvinince of needing to add "/corename" to the urls they connect from in their clients. : I would say it is a design problem which we should solve instead of : asking users to change the pros/cons of default core names were discussed at great length when multicore support was first added. Because of core swapping and path based requestHandler naming the confusion introduced by trying to have a default core winds up being *vastly* worse then the confusion of trying to explain why they should use "/solr/core/select" instead of "/solr/select" -Hoss
