geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruce Schuchardt (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-3085) Investigate replacement of getSocketHost(), getSocketPort(), getSocketAddress()
Date Thu, 14 Sep 2017 20:59:00 GMT

     [ https://issues.apache.org/jira/browse/GEODE-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bruce Schuchardt updated GEODE-3085:
------------------------------------
    Fix Version/s: 1.3.0

> 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
>             Fix For: 1.3.0
>
>
> 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)

Mime
View raw message