geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karen Smoler Miller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-283) Remove Gateway class if possible
Date Wed, 01 Feb 2017 20:50:51 GMT

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

Karen Smoler Miller commented on GEODE-283:
-------------------------------------------

There are no instances of the Gateway class in the documentation.

> Remove Gateway class if possible
> --------------------------------
>
>                 Key: GEODE-283
>                 URL: https://issues.apache.org/jira/browse/GEODE-283
>             Project: Geode
>          Issue Type: Sub-task
>          Components: wan
>            Reporter: Darrel Schneider
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> com.gemstone.gemfire.cache.util.Gateway used to be marked deprecated and was removed
along with the other deprecated Gateway classes. But rolling upgrade tests had problems because
the old and new members try to exchange a Gateway$OrderPolicy instance.
> So a stripped down version of Gateway was brought back for geode.
> But later a decision was made to not support rolling upgrade for the initial geode release
which means that Gateway and Gateway$OrderPolicy can be removed.
> If we end up needing to keep them then the javadocs in the new Gateway need to be improved.
They should probably just say it is for internal use only and it should be marked as deprecated
in 8.0.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message