Assembly: System.Net (in System.Net.dll)
In many instances, a PeerEndPoint is not the same as a peer host. A peer host has an instance within the ContactManager of the remote peer, and the relationship is that they have invited the peer to collaborate. An endpoint has a "Me" instance within its own contact manager and the peer host, but the relationship is not specified.
If the peer host is in the ContactManager, and the peer contact chooses not to Subscribe, its SubscriptionType can have a value of blocked, rather than deleting its entry from the host Contact Manager.
There is a many-to-many relationship between local peers, remote peers, peer hosts, and subscriptions. Subscriptions are per user, rather than per process, per application, or per domain. Consequently, the subscriptions associated with a PeerContact object are the list of contacts to which it has subscribed and from which it expects updates. Those contacts either have updated their own application, object, and presence information, or they have updated information regarding contacts in the ContactManager.
This property always returns true if the object is a PeerContact which represents the local or "Me" contact, since a contact is always subscribed to itself.