You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This operation blocks the calling thread until either all data written by the reliable DataWriter entities is acknowledged by all matched reliable DataReader entities, or else the duration specified by the max_wait parameter elapses, whichever happens first.
A return value of OK indicates that all the samples written have been acknowledged by all reliable matched data readers; a return value of TIMEOUT indicates that max_wait elapsed before all the data was acknowledged.
This is really useful for the following use cases.
safety-critical applications (e.g., autonomous vehicles, industrial automation, medical devices), ensuring data has been received before proceeding is crucial to avoid failures.
Useful in distributed systems where state synchronization is required before the next action can occur.
In systems where data integrity and order matter, waiting for an acknowledgment ensures that messages are not lost due to network issues.
The text was updated successfully, but these errors were encountered:
Overview
add the following
wait_for_all_acked
documentation with using examples.Client APIs
Examples
Description
This operation blocks the calling thread until either all data written by the reliable DataWriter entities is acknowledged by all matched reliable DataReader entities, or else the duration specified by the max_wait parameter elapses, whichever happens first.
A return value of OK indicates that all the samples written have been acknowledged by all reliable matched data readers; a return value of TIMEOUT indicates that max_wait elapsed before all the data was acknowledged.
This is really useful for the following use cases.
The text was updated successfully, but these errors were encountered: