You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bruce Schuchardt (JIRA)" <ji...@apache.org> on 2017/09/14 20:59:00 UTC
[jira] [Resolved] (GEODE-3085) Investigate replacement of
getSocketHost(), getSocketPort(), getSocketAddress()
[ https://issues.apache.org/jira/browse/GEODE-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Schuchardt resolved GEODE-3085.
-------------------------------------
Resolution: Not A Problem
ServerConnection holds the socket created for Protobuf clients and these methods work as-is. No additional work is required.
> Investigate replacement of getSocketHost(), getSocketPort(), getSocketAddress()
> -------------------------------------------------------------------------------
>
> Key: GEODE-3085
> URL: https://issues.apache.org/jira/browse/GEODE-3085
> Project: Geode
> Issue Type: Sub-task
> Components: client/server
> Reporter: Galen O'Sullivan
>
> Investigate replacement of getSocketHost(), getSocketPort(), getSocketAddress() in {{ServerConnection}}, given potentially messy interactions between new and old protocols.
> More specific details:
> {{ServerConnection}} has two methods, {{getSocketHost()}} and {{getSocketPort()}}, which are only used in a handful of places. Look at where they are used and either provide working implementations for {{NewClientServerConnection}} or remove their use / add a new API call on {{ServerConnection}}. Pay close attention that it doesn't tie into legacy commands we don't want to interact with in the new protocol.
> Also review getSocketAddress(), which may be tied to an observed but yet undocumented bug.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)