[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[dsdp-tcf-dev] [Bug 317845] 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
Eugene Tarassov <eugene.tarassov@xxxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #9 from Eugene Tarassov <eugene.tarassov@xxxxxxxxxxxxx> 2010-06-29 17:54:40 EDT ---
Fixed.
On meeting with John and Felix we agreed that we need to identify 3 types of
entities:
1. agent
2. service manager
3. peer
A TCF agent houses one or more service managers. A service manager has a one or
more services to expose to the world. The service manager creates one or more
peers to represent itself, one for every access path the agent is reachable by.
For example, in agents accessible via TCP/IP, the service manager would create
a peer for every subnet it wants to participate in.
In addition to peer ID, Locator service now supports two new peer properties:
"ServiceManagerID"
"AgentID"
--
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.
