Update documentation for Zenoh timestamping configuration#889
Update documentation for Zenoh timestamping configuration#889jordanburklund wants to merge 1 commit into
Conversation
| /// Whether data messages should be timestamped if not already. | ||
| /// Accepts a single boolean value or different values for router, peer and client. | ||
| /// | ||
| /// ROS setting: PublicationCache which is required for transient_local durability |
There was a problem hiding this comment.
I wasn't sure what to replace this with, so I left it as a WIP and will update it based on feedback from the maintainers.
|
I agree that the original comment is outdated. The However timestamping is still required, but only for
If You can see this running |
Description
Update documentation for Zenoh timstamping configurations for server and router configs. When testing locally with a simple "transient local" publisher and subscriber, the comment in the default configurations seems to be outdated. "transient local" topics were still working even when setting
timestamping: { enabled: false }for both sending topics locally on the same machine and sending topics between two different machines over the network.Is this user-facing behavior change?
No
Did you use Generative AI?
No
Additional Information