Revision as of 18:26, 25 August 2015 editTrappist the monk (talk | contribs)Administrators479,568 editsm clean up, replace/remove deprecated cs1|2 parameters; using AWB← Previous edit | Revision as of 14:22, 29 August 2015 edit undoKvng (talk | contribs)Extended confirmed users, New page reviewers107,833 edits Typed communication endpoint was WP:PRODedNext edit → | ||
Line 1: | Line 1: | ||
{{Refimprove|date=July 2015}} | {{Refimprove|date=July 2015}} | ||
{{mergefrom|Typed communication endpoint|date=July 2014}} | |||
A '''communication endpoint''' is a type of ]. 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 ] topic <ref>{{cite conference |first = Ran | last=Tao |author2=Stefan Poslad |author3=John Bigham |title = Resilient Delay Sensitive Load Management in Environment Crisis Messaging Systems. |conference = International Conference on Systems and Networks Communications (ICSNC) | year = 2013 | pages = 6–11}}</ref> | A '''communication endpoint''' is a type of ]. 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 ] topic <ref>{{cite conference |first = Ran | last=Tao |author2=Stefan Poslad |author3=John Bigham |title = Resilient Delay Sensitive Load Management in Environment Crisis Messaging Systems. |conference = International Conference on Systems and Networks Communications (ICSNC) | year = 2013 | pages = 6–11}}</ref> | ||
or a group in ]s.<ref>{{cite journal|last=Chockler |first= Gregory |author2=Idit Keidar |author3=Roman Vitenberg |title = Group communication specifications: a comprehensive study |journal=ACM Computing Surveys (CSUR) | year= 2001 |volume=33|issue=4| pages = 427–469}}</ref> | or a group in ]s.<ref>{{cite journal|last=Chockler |first= Gregory |author2=Idit Keidar |author3=Roman Vitenberg |title = Group communication specifications: a comprehensive study |journal=ACM Computing Surveys (CSUR) | year= 2001 |volume=33|issue=4| pages = 427–469}}</ref> | ||
Line 13: | Line 12: | ||
*] | *] | ||
*] | *] | ||
*] | |||
==References== | ==References== |
Revision as of 14:22, 29 August 2015
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
- Data terminal equipment
- Dial peer
- End system
- Host (network)
- Node (networking)
- Terminal (telecommunication)
References
- 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.
- Chockler, Gregory; Idit Keidar; Roman Vitenberg (2001). "Group communication specifications: a comprehensive study". ACM Computing Surveys (CSUR). 33 (4): 427–469.
This article relating to communication is a stub. You can help Misplaced Pages by expanding it. |