![]() Custom content filters, which allow users to “plugin” dedicated filters that take advantage of their specific application data types.Writer-Side content filtering to implement the DDS Content filters in the writer side, which enhances scalability and greatly reduces network traffic and CPU utilization.In addition, here are some of the enhanced (non-standard) capabilities that RTI Connext DDS supports, which are also not commonly found in open source distributions. RTI Persistence Service – Enables the ability to store data permanently and make it available to applications whenever they join the system.RTI Web Integration Service – Allows integration of web-based applications and services with RTI Connext DDS.Standard Services and Gateways - Includes Persistence Service, DDS-WEB Gateway, DDS-OPCUA Gateway and DDS-XRCE Gateway.Connext DDS supports UDP, TCP and Shared Memory (including Zero Copy Shared Memory) transports - Other distributions only support a UDP transport.Content Filtered Topics - This gives users the ability to select the data of interest based on the content, not just the Topic name.Coherent data across multiple Topics - This is implemented with coherent sets with presentation access scope.This capability complies with the DDS-XML standard. XML Application Language specification support - This provides users with QoS configuration through XML files.Request/reply functionality - This is part of the DDS-RPC OMG standard and provides users with an additional messaging paradigm to fit their use case.This is known as extensible types (DDS-XTYPES). Extensible data types definition - Defines data types in a more flexible way, with the ability to evolve over time without giving up portability, interoperability or the expressiveness of the DDS type system.Presentation Quality of Service (QoS) - The ability to control the order in which samples arrive at the subscriber.Language support - Connext DDS supports traditional C++, C++03, C++11, Java, Ada, C# and.If you aren't certain of what you will need as your project evolves, you should consider software that supports the complete DDS API.įor example, here are some of the standard OMG DDS capabilities that RTI Connext DDS supports that are not commonly found in open source distributions: When deciding between open source DDS and commercial DDS software, it's important to determine the DDS features that you need, then compare them to the features available with the DDS release you want to use. So, what should you consider when deciding between an open source DDS solution compared to a commercial solution? There are many commercial distributions that are available as well, of which the most widely-used is RTI Connext DDS. ![]() The DDS standard is an open standard and has open source implementations available. Open source software may be shared, modified and distributed, usually under an open source license. ![]() Open source software is computer software made available with its source code. An open standard is not the same thing as software that is open source. The Object Management Group ® (OMG ®) Data Distribution Service™ (DDS) standard is what is called an "open standard." This means that the standard is publicly available and provides a normative reference to help guarantee consistency, portability and interoperability, regardless of the DDS vendor. Why Open Source is Not the Same as Open Standard I thought it would be a good idea to update that blog with more recent information for 2020 and share it with you here. Since then, RTI Connext ® DDS has gained many new features, as have open source versions of DDS. In 2018, I posted a blog titled “ When is Open Source the Right Solution?” This question is still relevant, but as everyone knows, a lot can change in two years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |