geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Swapnil Bawaskar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
Date Wed, 01 Jun 2016 23:36:59 GMT

    [ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311366#comment-15311366
] 

Swapnil Bawaskar commented on GEODE-1467:
-----------------------------------------

Just because the Mgmt REST API was implemented first, it is (gemfire/v1) and the dev REST
api is (gemfire-api/v1). I think we should take this opportunity to rename the dev rest api
to (geode/v1) and the mgmt REST API to something like (geode-mgmt/v1 or geode/manage/v1).
Ideally in the long term, we should only expose one REST api for both data access and monitoring.

> 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)

Mime
View raw message