You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Galen O'Sullivan (JIRA)" <ji...@apache.org> on 2017/06/14 23:59:02 UTC
[jira] [Created] (GEODE-3084) investigate and possibly implement
NewClientServerConnection.GetProxyID
Galen O'Sullivan created GEODE-3084:
---------------------------------------
Summary: investigate and possibly implement NewClientServerConnection.GetProxyID
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
There is some logic around unique client IDs that is used by {{ServerConnection}}. Look 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 that ticket), which seem to be used mostly for management and reporting.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)