[
https://issues.apache.org/jira/browse/SOLR-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636891#comment-13636891
]
Shawn Heisey commented on SOLR-4700:
------------------------------------
I had a thought - what if we make XXX configurable, defaulting to some
reasonable string? After I had that thought, I realized it might make it even
harder for this issue to gain support, because it would remove URL consistency
and add complexity to client code. I'm just putting the thought out there, not
making it an official part of my proposal at this time.
> Move Solr client API URLs to their own context namespace
> --------------------------------------------------------
>
> Key: SOLR-4700
> URL: https://issues.apache.org/jira/browse/SOLR-4700
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.3
> Reporter: Shawn Heisey
> Fix For: 5.0
>
>
> If we moved the client API base URLs to their own URL namespace, it would
> free up the 'top level' URL namespace for other uses. This would mean moving
> http://host:port/solr/YYY to http://host:port/solr/XXX/YYY - where YYY is a
> core or collection name and XXX is some string yet to be determined.
> The existing URL setup is so widely used that we probably would not be able
> to remove backwards compatibility until at least 6.0.
> See discussion on SOLR-4431.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
