[
https://issues.apache.org/jira/browse/GEODE-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-3518:
-------------------------------------
Description:
The `ServerLocator` currently knows how to use the transport layer as well as
how to get the requested information out of the Locator. We should split this
up into at least a class that deals with transport and a separate class (or
multiple) that know how to do the business logic of getting the information
requested.
We are already duplicating some of the business logic in the
`GetAvailableServersOperationHandler`. Both the `ServerLocator` and the handler
should be able to use the same business logic. Maybe we could/should even use
the handler in the `ServerLocator`?
was:The `ServerLocator` currently knows how to use the transport layer as
well as how to get the requested information out of the Locator. We should
split this up into at least a class that deals with transport and a separate
class (or multiple) that know how to do the business logic of getting the
information requested.
> Refactor ServerLocator
> ----------------------
>
> Key: GEODE-3518
> URL: https://issues.apache.org/jira/browse/GEODE-3518
> Project: Geode
> Issue Type: Task
> Reporter: Alexander Murmann
>
> The `ServerLocator` currently knows how to use the transport layer as well as
> how to get the requested information out of the Locator. We should split this
> up into at least a class that deals with transport and a separate class (or
> multiple) that know how to do the business logic of getting the information
> requested.
> We are already duplicating some of the business logic in the
> `GetAvailableServersOperationHandler`. Both the `ServerLocator` and the
> handler should be able to use the same business logic. Maybe we could/should
> even use the handler in the `ServerLocator`?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
