Misplaced Pages

Communication endpoint

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.

This is an old revision of this page, as edited by Calamarain (talk | contribs) at 14:46, 18 November 2019 (Undid revision 926708387 by 2601:82:C380:26C0:C9D5:1E6C:97AD:CF26 (talk)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 14:46, 18 November 2019 by Calamarain (talk | contribs) (Undid revision 926708387 by 2601:82:C380:26C0:C9D5:1E6C:97AD:CF26 (talk))(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Communication endpoint" – news · newspapers · books · scholar · JSTOR (July 2015) (Learn how and when to remove this message)

A communication endpoint is a type of communication network node. It is an interface exposed by a communicating party or by a communication channel. An example of the latter type of a communication endpoint is a publish-subscribe topic or a group in group communication systems.

A communication endpoint is a discoverable node of communication whose scope may be varied to narrow or broaden the discovery zone. Endpoints facilitate a standard programmable layer of abstraction whereby heterogeneous software systems and/or subsystems may communicate with each other and that the means of communication are decoupled from the communicating subsystems.

See also

References

  1. Tao, Ran; Stefan Poslad; John Bigham (2013). Resilient Delay Sensitive Load Management in Environment Crisis Messaging Systems. International Conference on Systems and Networks Communications (ICSNC). pp. 6–11.
  2. Chockler, Gregory; Idit Keidar; Roman Vitenberg (2001). "Group communication specifications: a comprehensive study". ACM Computing Surveys. 33 (4): 427–469. CiteSeerX 10.1.1.29.2184. doi:10.1145/503112.503113.
Categories: