Content deleted Content added
KAROUIRamzi (talk | contribs) |
KAROUIRamzi (talk | contribs) No edit summary |
||
Line 33:
* 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
DDS also automatically handles hot-swapping redundant publishers if the primary fails. {{citation needed|date=October 2019}} 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.
Line 73:
The specification provides mappings for the [[application programming interface]] (API) specified in DDS-XTypes, and accessing [[quality of service]] (QoS) profiles specified in DDS-CCM.
Extensible and Dynamic Topic Types for DDS (DDS-XTypes) provided support for data-centric publish-subscribe communication where topics are defined with specific data structures. To be ''extensible'', DDS topics use data types defined before compile
A [[Unified Modeling Language]] (UML) profile specified DDS domains and topics to be part of the analysis and design modeling.<ref>UML Profile for Data Distribution, version: 1.0, http://www.omg.org/cgi-bin/doc?ptc/10-05-17.pdf </ref> This specification also defined how to publish and subscribe objects without first describing the types in another language, such as XML or OMG IDL.<ref>DDS-Java: Java 5 Language PSM for DDSVersion 1.0, ptc/2012-12-01, March 2013 http://www.omg.org/spec/DDS-Java/1.0/Beta3/PDF</ref>
An [[interface definition language]] (IDL) was specified in 2014 independently from the [[Common Object Request Broker Architecture]] (CORBA) specification chapter 3. This IDL 3.5 was compatible with the CORBA 3 specification, but extracted as its own specification allowing it to evolve independently from CORBA.<ref>{{Cite web |title= Interface Definition Language (IDL), Version 3.5 |date= March 1, 2014 |publisher= OMG |url= http://www.omg.org/spec/IDL35/3.5/ |accessdate= November 9, 2016 |archive-url= https://web.archive.org/web/20170121033326/http://www.omg.org/spec/IDL35/3.5/ |archive-date= January 21, 2017 |url-status= dead }}</ref>
Starting with DDS version 1.4 in 2015, the optional DLRL layer was moved to a separate specification.<ref>{{Cite web |title= DDS Data Local Reconstruction Layer (DDS-DLRL) |date= April 2015 |url= http://www.omg.org/spec/DDS-DLRL/ |accessdate= November 9, 2016 }}</ref>
== Commercial Editors and Opensource Editions ==
Several editors provide OMG DDS compliant implementations, namely:
* ADLINK, [https://www.adlinktech.com/en/data-distribution-service]
* eProsima, [https://www.eprosima.com/index.php/]
* Kongsberg, [https://kongsberggeospatial.com/]
* Milsoft [http://www.milsoft.com.tr/, http://www.milsoft.com.tr/]
* [https://objectcomputing.com/ ]
* RTI, [https://www.rti.com/en/]
* Twinoaks, [http://www.twinoakscomputing.com/]
Some DDS implementations are opensource with commercially support offerings, such as:
* [[Cyclone DDS]] [http://github.com/eclipse-cyclonedds/cyclonedds]
* [[FastRTPS]] [https://github.com/eProsima/Fast-DDS]
* [[OpenDDS]] [https://github.com/objectcomputing/OpenDDS]
* [[Opensplice]] DDS community edition]] https://github.com/ADLINK-IST/opensplice
== See also ==
Line 83 ⟶ 101:
* [[Middleware]]
* [[Open architecture computing environment]]
* [[Object Management Group]] (OMG), the standards body that developed the specification
== References ==
| |||