[
https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356579#comment-15356579
]
Nitin Lamba commented on GEODE-1467:
------------------------------------
+1 [~swapnil.bawaskar]
Once the authentication/ authorization is in place, the APIs can certainly move
to a common end-point. However, last checked with the team, it seemed that
management REST required a lot more re-engineering. For example, some of the
data returned is in complicated tabular structure rather than JSON. Jens Deppe
may have some more thoughts on the current state.
This JIRA is only for a quick rename fix.
> Branding: Rename servlet URLs from gemfire to geode
> ---------------------------------------------------
>
> Key: GEODE-1467
> URL: https://issues.apache.org/jira/browse/GEODE-1467
> Project: Geode
> Issue Type: Improvement
> Reporter: Nitin Lamba
>
> There are a few locations where gemfire references are used (excluding
> package hierarchy covered in GEODE-37):
> 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1)
> 2. extension modules (http session mgmt)
> 3. others (spring-data?)
> (2) and (3) can be hairy as it may impact existing applications. A change
> post 1.0 would create complexity, therefore, should be carefully considered
> for 1.0 release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
