You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Brian Baynes (JIRA)" <ji...@apache.org> on 2017/08/31 23:26:00 UTC
[jira] [Updated] (GEODE-3084) Investigate unique client IDs in
server connection class
[ https://issues.apache.org/jira/browse/GEODE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Baynes updated GEODE-3084:
--------------------------------
Description:
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.
was:
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.
We can safely assume (for now) that each connection with the new client protocol is coming from a different client.
Probably what we will do is make a new subclass of ClientProxyID that is unique for each new client protocol connection.
This is related to {{ServerConnection}'s {{getSocketHost()}} and {{getSocketPort()}} (see GEODE-3085), which seem to be used mostly for management and reporting.
Summary: Investigate unique client IDs in server connection class (was: investigate and possibly implement NewClientServerConnection.GetProxyID)
> 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
>
> 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)