Back to Intro Page

Contents

Possible problems and known errors within the OpenSplice DDS DDSI implementation.

Limitations

The current implementation has limited functionality, but this will be extended in future releases. Known limitations of the current implementation are:

• Only BEST_EFFORT reliability QoS has been implemented.
• Only VOLATILE durability QoS has been implemented.
• Fragmentation of large messages has not been implemented. Therefore messages larger then the configured fragment size cannot be sent or received.
• QoS modifications after the creation of an entity is not possible.

Known interoperability issues

Key hash

The Key Hash provides a hint for the key that uniquely identifies the data-object that is being changed within the set of objects that have been registered by a DDS DataWriter. Nominally the key is part of the serialized data of a data submessage. Using the key hash may benefit implementations by providing a faster alternative than deserializing the full key from the received data-object. Whether this is faster depends on the way instances are stored internally though. Therefore implementations must also support sending/receiving serialized data besides or instead of the key hash only.

This implementation only supports sending/receiving key hashes for keys up to 16 bytes. For larger keys, the implementation omits the key hash and requires the serialized data within a data sub-message. This means other implementations must also send this serialized data and be able to handle incoming dispose and unregister data submessages with serialized data (and without key hash) correctly.

Top