Where to get Support

DDS mailing lists

The DDS mailing lists are available through the SourceForge project page. The archives of previous messages are searchable.

Online Documentation

View the online documentation for OpenDDS.

The Code

The code is commented. Take a look in the header and class files, also see the doxygen.
Some documentation is included with the code in the DDS_ROOT/docs directory.
Code examples are included in the OpenDDS distribution in the DDS_ROOT/examples directory.

Commercial Support

OCI's Subject Matter Experts (SMEs) are available to provide 24/7 real-time technical support for OpenDDS. Please contact us for details.

OCI can help you to successfully architect and deliver your solution by drawing on the experience of seasoned architects who have extensive experience in today's middleware technologies and who understand how to leverage the power of OpenDDS.

Please contact us at sales@ociweb.com for additional information.

Features that need Sponsoring

The Data Local Reconstruction Layer (DLRL) is very attractive and we expect developers to require it in future versions of OpenDDS. While OCI has developed a comprehensive implementation of DLRL, in Java and C++, it is not available under an open source model.

We also anticipate using the extensible transport framework (ETF) to provide additional transports, for different industry segments, and potentially a “DDS to Pub/Sub Gateway” to accommodate the many legacy systems’ protocols.

Along with Gateways we expect to develop migration strategies for those clients who wish to consolidate their pub/sub infrastructure into a standards-based, open source framework.

Communicating securely over real-time, deadline-scheduled, publish-subscribe middleware is challenging. A security management framework for OpenDDS is planned that supports authentication, data integrity, key management (symmetric and asymmetric), and non-repudiation. The framework would enable users of OpenDDS to configure their own encryption and hashing algorithms and other security aspects. The implementation of this framework will not conflict with International Traffic in Arms Regulations (ITAR); encryption strength and the implementation thereof is still the responsibility of the end user in consonance with local laws. The goal is to minimize the impact of the additional security capabilities on the performance and predictability of the data communication and to integrate the new capabilities into the existing overall OpenDDS architecture. Funding is needed to implement the security management framework for OpenDDS.