[
https://issues.apache.org/jira/browse/TS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250870#comment-14250870
]
Eric Schwartz commented on TS-2157:
-----------------------------------
A proposal that I think might be clearer:
Instead of src_addr and dst_addr (which gets confusing because of implied
directionality) we instead store local_addr and remote_addr.
remote_addr would correspond to what addr is now, storing the addr of the
remote host to which ats is connecting (both in the case of server_info and
client_info to go off of the previous comment's example)
local_addr would then store the information for the local IpEndpoint for the
ATS host. This would make implementation of TS-2152 (with which i am also
conveniently tasked) much more straightforward, I think.
> Replace "addr" with appropriate "src_addr" and "dst_addr" in
> ConnectionAttributes
> ---------------------------------------------------------------------------------
>
> Key: TS-2157
> URL: https://issues.apache.org/jira/browse/TS-2157
> Project: Traffic Server
> Issue Type: New Feature
> Components: Network
> Reporter: Leif Hedstrom
> Assignee: Eric Schwartz
> Fix For: 6.0.0
>
>
> This would more clearly let us encapsulate the two endpoint's (IpEndpoint)
> for each connection. In addition, we ought to be able to remove the "port"
> member from ConnectionAttributes as well, and its convoluted and overloaded
> semantics. The appropriate IpEndpoint (src_addr or dst_addr) would hold the
> port information as necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
