[
https://issues.apache.org/jira/browse/GEODE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Bawaskar updated GEODE-3084:
------------------------------------
Fix Version/s: (was: 1.3.0)
> Investigate unique client IDs in server connection class
> --------------------------------------------------------
>
> Key: GEODE-3084
> URL: https://issues.apache.org/jira/browse/GEODE-3084
> Project: Geode
> Issue Type: Sub-task
> Components: client/server
> Reporter: Galen O'Sullivan
> Assignee: Bruce Schuchardt
>
> Investigate use of unique client IDs in server connection class (see below)
> -- gather info on complexity/impact that will inform a decision to fix (or
> not).
> There is some logic around unique client IDs that is used by
> {{ServerConnection}}. Look at what calls this (outside of the {{Command
> classes}}, which shouldn't be calling {{NewClientServerConnection}} objects)
> and determine if we need to make our own {{ClientProxyID}}s or if the
> interface can be abstracted in a better way.
> This is related to {{ServerConnection}'s {{getSocketHost()}} and
> {{getSocketPort()}} (see GEODE-3085), which seem to be used mostly for
> management and reporting.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
