Content deleted Content added
→History: wording |
review: link first occurrence. ce. |
||
Line 1:
{{Use American English|date=January 2020}}
In [[computer networking]], a '''reliable''' protocol is a [[communication protocol]] that notifies the sender whether or not the delivery of data to intended recipients was successful. Reliability is a synonym for '''assurance''', which is the term used by the [[ITU]] and [[ATM Forum]].
Reliable protocols typically incur more overhead than unreliable protocols, and as a result, function more slowly and with less scalability. This often is not an issue for [[unicast]] protocols, but it may become a problem for [[reliable multicast]] protocols.
Line 40:
Strong reliability properties are offered by [[group communication system]]s (GCSs) such as [[IS-IS]], [[Appia framework]], [[Spread (group communication system)|Spread]], [[JGroups]] or [[QuickSilver Scalable Multicast]]. The [[QuickSilver Properties Framework]] is a flexible platform that allows strong reliability properties to be expressed in a purely declarative manner, using a simple rule-based language, and automatically translated into a hierarchical protocol.
One
[[IEEE 802.11]] attempts to provide reliable service for all traffic. The sending station will resend a frame if the sending station doesn't receive an ACK frame within a predetermined period of time.<!--[[User:Kvng/RTH]]-->
==Real-time systems==
|