Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[dsdp-tcf-dev] [Bug 317845] New: TCF Peer accessible via two networks appear as two distinct peers 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=317845 
Product/Component: Target Management / TCF

           Summary: TCF Peer accessible via two networks appear as two
                    distinct peers
    Classification: DSDP
           Product: Target Management
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P3
         Component: TCF
        AssignedTo: dsdp.tm.tcf-inbox@xxxxxxxxxxx
        ReportedBy: john.cortell@xxxxxxxxxxxxx
         QAContact: martin.oberhuber@xxxxxxxxxxxxx


An agent running on a host with two network interfaces, that has access to a
peer on a remote host via both networks, will see the peer as two distinct
peers. This happens because an agent advertises (through Discovery) its peers
to all subnets it is bound to. Each subnet gets a different peer
representation; the ADDR_IP_HOST of each is the network interface of the
hosting agent for the respective subnet. 

There currently is no standardized way for the observing host to determine that
the two actually represent a single peer. The observing host has to simply pick
one or prompt the user to choose. If the latter, then the user is likely to be
confused, as he may not be expecting two peers, and he will not realize the two
choices are really the same peer with a different network access path. 

TCF needs to allow clients to determine that the two are really the same. It
would allow the client app to present the situation a lot more intelligently to
the user. E.g., the app might expose a preference:

(a) mask the fact that there are two; just use the first and ignore the second
(b) show both to the user, but in a way that reflects one peer with two network
paths

The latter may be useful where one network path behaves differently than
another.

A solution would be to introduce a core peer attribute that will uniquely
identify a running agent instance on a host.

-- 
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

Back to the top