As a lot of you know, the DDS-RTPS interoperability protocol for DDS most frequently runs on top of UDP/IP. DDS implementations, RTI Data Distribution Service included, provide support for a number of other lower-level transport protocols. But UDP provides the greatest flexibility in terms of both reliability and timing, and it’s the transport that the [...]
Archive for the ‘Future directions’ Category
TCP Transport for DDS
Posted in Future directions, Standards on March 30, 2011 | Leave a Comment »
DDS Update: New C++ and Java APIs, Security Enhancements
Posted in Future directions, Standards on December 10, 2010 | Leave a Comment »
At this week’s OMG meeting, C++ and Java APIs for DDS were recommended for adoption and a DDS security RFP was issued.
OMG Update
Posted in Future directions, Standards on April 29, 2010 | Leave a Comment »
Last month, the Object Management Group (OMG) held a technical meeting, sponsored in part by RTI, in Jacksonville, Florida. There were a lot of important developments, and I’d like to give you a short recap: Perhaps the most important milestone for DDS followers was the recommendation for adoption of the new specification Extensible and Dynamic [...]
In Progress at OMG: Extensible and Dynamic Types
Posted in Future directions, Standards on September 1, 2009 | 1 Comment »
DDS is popular, and addresses a number of important use cases that are not addressed by other specifications, but that doesn’t mean it’s perfect. The DDS community — including both customers and vendors — is active within the OMG to address additional areas in need of standardization. I thought I’d share one of those areas [...]
Designing information models for distributed applications
Posted in Applications, Best practices, Future directions on April 20, 2009 | Leave a Comment »
The technologists in edge environment spend significant time tuning the network links, but they often miss opportunities to make optimal use of available bandwidth by not focusing (enough) on tuning the data model. This (relative) lack of attention to the data model, while regrettable, can be better understood if we account that until recently, edge devices were weak (could not collect or process enough information), few (not choking the network, though bandwidth is always an issue), or not (richly) context-aware (taking advantage of other information available on the network) The science of tuning the information model for a distributed application can benefit from the advances in building information models for the enterprise applications.