[GEODE-3084] Investigate unique client IDs in server connection class

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Component/s: client/server
• Assignee: Bruce J Schuchardt
• Reporter: Galen O'Sullivan
• Created: 14/Jun/17 23:58
• Updated: 13/Oct/17 20:36
• Resolved: 14/Sep/17 21:04

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.