Content deleted Content added
Line 12:
The DDS publish-subscribe model virtually eliminates complex network programming for distributed applications. {{citation needed}}
DDS supports mechanisms that go beyond the basic publish-subscribe model. {{citation needed}} The key benefit is that applications that use DDS for their communications are decoupled. Little design time needs be spent on handling their mutual interactions. In particular, the applications never need information about the other participating applications, including their existence or locations. DDS transparently handles message delivery without requiring intervention from the user applications, including:
* determining who should receive the messages
Line 18:
* what happens if messages cannot be delivered
DDS allows the user to specify [[quality of service]] (QoS) parameters to configure discovery and behavior mechanisms up-front. By exchanging messages anonymously, DDS simplifies distributed applications and encourages modular, well-structured programs. {{citation needed}}
DDS also automatically handles hot-swapping redundant publishers if the primary fails. {{citation needed}} Subscribers always get the sample with the highest priority whose data is still valid (that is, whose publisher-specified validity period has not expired). It automatically switches back to the primary when it recovers, too.
=== Interoperability ===
| |||