[jboss-jira] [JBoss JIRA] Resolved: (JGRP-1240) TCP: add physical address of peer to physical address cache (bypassing discovery)

[Bela Ban (JIRA)]

     [ https://jira.jboss.org/browse/JGRP-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban resolved JGRP-1240.
----------------------------

    Resolution: Won't Fix


> TCP: add physical address of peer to physical address cache (bypassing discovery)
> ---------------------------------------------------------------------------------
>
>                 Key: JGRP-1240
>                 URL: https://jira.jboss.org/browse/JGRP-1240
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 2.11
>
>
> When we use TCP, the physical address information of a peer P connecting to us should always be available !
> E.g.currently, if we have A and B, and A wants to send a message to B, but doesn't have B's physical address, if A is connected to B, then we can get that information from the connection map in TCP !
> We should therefore add the physical address information for B when B connects to us, or we connect to B !
> Issues:
> - What if B binds to address 10.1.1.1, but  - when B connects to us (A: 192.16.8.1.5) - its peer address is 192.168.1.3 ? Is this possible at all ? Does the routing table force a different peer address of B: 192.168.x.x rather than 10.1.x.x ?
> - Although we might be able to get the physical address of B, we don't get its logical name ! How would we do that, discovery ?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira