[
https://issues.apache.org/jira/browse/GEODE-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109128#comment-16109128
]
ASF GitHub Bot commented on GEODE-3284:
---------------------------------------
Github user pivotal-amurmann commented on a diff in the pull request:
https://github.com/apache/geode/pull/673#discussion_r130646340
--- Diff: geode-protobuf/src/main/proto/clientProtocol.proto ---
@@ -43,13 +43,12 @@ message Request {
GetAllRequest getAllRequest = 5;
RemoveRequest removeRequest = 6;
RemoveAllRequest removeAllRequest = 7;
- ListKeysRequest listKeysRequest = 8;
CreateRegionRequest createRegionRequest = 21;
DestroyRegionRequest destroyRegionRequest = 22;
- PingRequest pingRequest = 41;
- GetServersRequest getServersRequest = 42;
+// PingRequest pingRequest = 41;
--- End diff --
what are you saving it for?
> New flow: getAvailableServers
> -----------------------------
>
> Key: GEODE-3284
> URL: https://issues.apache.org/jira/browse/GEODE-3284
> Project: Geode
> Issue Type: Sub-task
> Components: client/server
> Reporter: Brian Baynes
>
> As a Geode client user, I'd like to be able to know all available servers in
> a grid in order to support operations targeting any available server.
> Create op handler for getAvailableServers message, following proto message
> definition.
> Client should be able to complete getAvailableServers, receiving all servers
> available in grid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
