[jira] [Updated] (TS-2157) Replace "addr" with appropriate "src_addr" and "dst_addr" in ConnectionAttributes
[ https://issues.apache.org/jira/browse/TS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2157: -- Fix Version/s: (was: 6.1.0) 6.0.0 > 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)
[jira] [Updated] (TS-2157) Replace "addr" with appropriate "src_addr" and "dst_addr" in ConnectionAttributes
[ https://issues.apache.org/jira/browse/TS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-2157: Fix Version/s: (was: 6.0.0) 6.1.0 > 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.1.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)
[jira] [Updated] (TS-2157) Replace "addr" with appropriate "src_addr" and "dst_addr" in ConnectionAttributes
[ https://issues.apache.org/jira/browse/TS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll updated TS-2157: Assignee: Eric Schwartz > 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)
[jira] [Updated] (TS-2157) Replace "addr" with appropriate "src_addr" and "dst_addr" in ConnectionAttributes
[ https://issues.apache.org/jira/browse/TS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-2157: --- Fix Version/s: (was: sometime) 6.0.0 > 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 > 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)
[jira] [Updated] (TS-2157) Replace "addr" with appropriate "src_addr" and "dst_addr" in ConnectionAttributes
[ https://issues.apache.org/jira/browse/TS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2157: -- Fix Version/s: 5.0.0 > 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 > Fix For: 5.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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2157) Replace "addr" with appropriate "src_addr" and "dst_addr" in ConnectionAttributes
[ https://issues.apache.org/jira/browse/TS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2157: -- Summary: Replace "addr" with appropriate "src_addr" and "dst_addr" in ConnectionAttributes (was: Replace "add" with appropriate "src_addr" and "dst_addr" in ConnectionAttributes) > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
