geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darrel Schneider (JIRA)" <>
Subject [jira] [Commented] (GEODE-243) Remove the old client/server bridge classes
Date Thu, 10 Sep 2015 17:39:46 GMT


Darrel Schneider commented on GEODE-243:

This task is completed on the feature/GEODE-243 branch.
Merging this work to develop will break anyone using any of the old Bridge apis. The "bridge-server"
element has also been removed from the newest xsd so if someone tries to write a cache.xml
using the new xsd they would need to use "cache-server" instead.
Changes were also made to internal classes that will prevent a rolling upgrade of a system
from an old version that had the bridge code to a new version that does not have the bridge
code. For example the old product had a class named BridgeServerProfile that is sent from
a server to the locator. This class has been renamed to CacheServerProfile. So an old server
can no longer talk to a new locator and a new server can not talk to an old locator.
The GEODE-77 (jgroup removal) work also prevents rolling upgrade so I think it is ok for this
task to do so.

> Remove the old client/server bridge classes
> -------------------------------------------
>                 Key: GEODE-243
>                 URL:
>             Project: Geode
>          Issue Type: Sub-task
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>   Original Estimate: 72h
>  Remaining Estimate: 72h
> The following classes should be removed. They were part of a very old client/server implementation
that has been replaced by pools.
> - com.gemstone.gemfire.cache.util.BridgeClient
> - com.gemstone.gemfire.cache.util.BridgeLoader
> - com.gemstone.gemfire.cache.util.BridgeWriter
> - com.gemstone.gemfire.cache.util.BridgeServer
> - com.gemstone.gemfire.cache.util.BridgeMembership
> - com.gemstone.gemfire.cache.util.BridgeMembershipEvent
> - com.gemstone.gemfire.cache.util.BridgeMembershipListener
> - com.gemstone.gemfire.cache.util.BridgeMembershipListenerAdapter
> - com.gemstone.gemfire.cache.util.BridgeWriterException
> - com.gemstone.gemfire.cache.util.EndpointDoesNotExistException
> - com.gemstone.gemfire.cache.util.EndpointException
> - com.gemstone.gemfire.cache.util.EndpointExistsException
> - com.gemstone.gemfire.cache.util.EndpointInUseException
> - com.gemstone.gemfire.cache.util.IncompatibleVersionException
> - com.gemstone.gemfire.cache.util.ServerRefusedConnectionException
> - com.gemstone.gemfire.cache.util.UnknownVersionException
> - com.gemstone.gemfire.cache.util.VersionException
> unit tests may still exist that test this older implementation. They can be removed since
a corresponding test using pools also exists.
> This task may be more work and it would be wise to have someone who understands the old
code involved in removing it.

This message was sent by Atlassian JIRA

View raw message