8. Release Notes¶
Contents:
- 8.1. Supported Platforms and Programming Languages
- 8.2. Compatibility
- 8.3. What’s New in 3.0.2
- 8.3.1. Micro Application Generation examples now use ignore_loopback_interface
- 8.3.2. Support for custom prefix properties when configuring the security plugin
- 8.3.3. Updated OpenSSL version
- 8.3.4. Support for payload encryption between local endpoints
- 8.3.5. Performance optimization on serialization/deserialization for sequences with complex elements
- 8.3.6. Protocol improvements for fragmented samples
- 8.4. What’s Fixed in 3.0.2
- 8.4.1. Sample filtering methods are always added to the subscriber code for C
- 8.4.2. Incorrect text in error message when specifying security properties programmatically
- 8.4.3. Invalid serialization of samples with types containing primitive members that require padding
- 8.4.4. Compiler warning in FreeRTOS port
- 8.4.5. HelloWorld_dpde_waitset C++ example uses wrong loop variable for printing data
- 8.4.6. Warning DDSC_LOG_DESERIALIZE_UNKNOWN_PID_EC is logged when security is disabled
- 8.4.7. High memory usage with security enabled
- 8.4.8. FlatData: possible compilation error building data for a type with a sequence with Traditional C++
- 8.4.9. FlatData: Conversion warning on some platforms
- 8.4.10. FlatData: Bad performance of PrimitiveSequenceBuilder:add_n
- 8.4.11. Large timeout values, e.g liveliness and deadline, may cause segmentation fault
- 8.4.12. Generated public APs to serialize/deserialize samples do not work within an IDL module when the -namespace option is used with rtiddsgen
- 8.4.13. Configuring the DPDE Discovery Plugin with max_samples_per_remote_builtin_writer > 1 may result in discovery samples not being processed
- 8.4.14. Read/take APIs returned more than depth samples if an instance returned to alive without application reading NOT_ALIVE sample
- 8.4.15. An application may have terminated with a segmentation fault if OSAPI_Semaphore_give() was called from one thread while another called OSAPI_Semaphore_delete()
- 8.4.16. PUBLICATION_MATCHED_STATUS and SUBSCRIPTION_MATCHED_STATUS may never trigger a WaitSet if the status is enabled after the DomainParticipant is enabled
- 8.5. Previous Releases
- 8.6. Known Issues
- 8.6.1. Flow Controllers require RTOS
- 8.6.2. Using OpenSSL 1.0.x and using OpenSSL APIs outside of the RTI Connext DDS Micro libraries may lead to a crash
- 8.6.3. LatencyBudget is not part of the DataReaderQos or DataWriterQos policy
- 8.6.4. Porting Guide does not include information about shared memory support