Release Notes

• 1. Supported Platforms
• 2. Compatibility
• 3. What’s New in 7.7.0
  • 3.1. XML option to enable new synchronization built-in content filter
  • 3.2. Improved performance when <purge_samples_after_acknowledgment> set to TRUE
  • 3.3. Ensure proper synchronization of dispose messages when <propagate_dispose> and <data_synchronization> are enabled
  • 3.4. Performance improvements with Application Acknowledgement enabled in Persistence Service DataWriter
  • 3.5. Monitor Persistence Service health with lightweight HTTP server
  • 3.6. Reduced discovery traffic between participants and Persistence Service when synchronization enabled
  • 3.7. Improved diagnostics with extended SQLite error codes in Persistence Service database
• 4. What’s Fixed in 7.7.0
  • 4.1. Usability
  • 4.2. Performance and Scalability
  • 4.3. Hangs
  • 4.4. Memory Leaks/Growth
  • 4.5. Crashes
  • 4.6. Data Corruption
  • 4.7. Vulnerabilities
  • 4.8. Other
• 5. Previous Releases
  • 5.1. What’s New in 7.6.0
  • 5.2. What’s Fixed in 7.6.0
  • 5.3. What’s New in 7.5.0
  • 5.4. What’s Fixed in 7.5.0
  • 5.5. What’s Fixed in 7.4.0
• 6. Known Issues
  • 6.1. Coherent Changes not Propagated as Coherent Set
  • 6.2. TopicQueries not Supported in PERSISTENT Mode
  • 6.3. <comm_ports/mapping> not supported when using Real-Time WAN Transport
  • 6.4. Persistence Service DataReaders Ignore Serialized Key Propagated with Dispose Updates
  • 6.5. Some tags in the XML configuration must be grouped in a strict order
• 7. Available Documentation

• Copyrights and Notices