Uploaded image for project: 'JGroups'
  1. JGroups
  2. JGRP-1240

TCP: add physical address of peer to physical address cache (bypassing discovery)

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Won't Do
    • Icon: Major Major
    • 2.11
    • None
    • None
    • 0
    • 0% 0%

      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 ?

            rhn-engineering-bban Bela Ban
            rhn-engineering-bban Bela Ban
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: