Revision as of 21:02, 23 August 2023 edit Dicklyon (talk \| contribs) Autopatrolled, Extended confirmed users, Rollbackers 486,013 edits m case fix (via WP:JWB) ← Previous edit		Revision as of 14:10, 22 September 2023 edit undo Kvng (talk \| contribs) Extended confirmed users, New page reviewers 116,060 edits →Implementations: rm redlink Next edit →
Line 39: A reliable delivery protocol can be built on an unreliable protocol. An extremely common example is the layering of [[Transmission Control Protocol]] on the [[Internet Protocol]], a combination known as [[TCP/IP]]. 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 protocol that implements reliable messaging is [[WS-ReliableMessaging]], which handles reliable delivery of [[SOAP]] messages.<ref>[http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-rm/ws-reliablemessaging200502.pdf WS-ReliableMessaging specification (PDF)]</ref>

Reliability (computer networking): Difference between revisions