[ 
https://issues.apache.org/jira/browse/GEODE-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045976#comment-17045976
 ] 

ASF subversion and git services commented on GEODE-7808:
--------------------------------------------------------

Commit a82d990435bf2bb30d45a021f5ccb5b59149f3d7 in geode's branch 
refs/heads/feature/GEODE-7808 from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a82d990 ]

GEODE-7808 standardize on use of LocatorAddress/HostAddress

removed HostAddress
renamed LocatorAddress to HostAndPort
modified TcpClient methods to take a HostAndPort argument instead of
InetAddress
modified SocketCreator to take a HostAndPort argument instead of
InetAddress


> standardize on use of LocatorAddress/HostAddress for connection formation
> -------------------------------------------------------------------------
>
>                 Key: GEODE-7808
>                 URL: https://issues.apache.org/jira/browse/GEODE-7808
>             Project: Geode
>          Issue Type: Improvement
>          Components: membership, messaging
>            Reporter: Bruce J Schuchardt
>            Assignee: Bruce J Schuchardt
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> We currently use InetAddress and InetSocketAddress in many places to identify 
> locators, servers and peers.  Some work has been done in the past couple of 
> years to reduce the use of these in order to accommodate changes in IP 
> addresses due to various causes.  The class LocatorAddress was created to 
> help with this and it is able to hold a host name without resolving it until 
> that resolution is needed to form a tcp/ip connection.
> These days we are seeing more and more movement into cloud computing and the 
> need to accommodate IP address changes is becoming a bigger issue.  To that 
> end we would like to  change our primary client/server and WAN communication 
> interfaces to stop taking InetAddresses and InetSocketAddresses as arguments 
> and, instead, take something like a LocatorAddress that can hold an 
> unresolved hostname that our communication implementations will resolve when 
> needed.
> To that end we should also remove the hostname->inetaddress cache in 
> SocketCreator and rely on the operating system's DNS cache.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to