zenoh unifies data in motion, data in-use, data at rest and computations. It carefully blends traditional pub/sub with geo-distributed storages, queries and computations, while retaining a level of time and space efficiency that is well beyond any of the mainstream stacks.
Change all the admin and plugin key expressions to be in the following spaces:
@/<zenohid>/router/**@/<zenohid>/peer/**@/<zenohid>/client/**@/<zenohid>/dds/**@/<zenohid>/ros1/**@/<zenohid>/ros2/**@/<zenohid>/@ros2_pub_cache/**@/<zenohid>/@ros2_lv/**@/<zenohid>/mqtt/**@/<zenohid>/@storage/digest/**@/<zenohid>/@storage/align/**
The reasons behind those changes are:
Gather all internal management keys under a common prefix.
Allow to access all infos about a Zenoh node in one get.
Allow to apply a ZenohID based routing to the @ namespace in the future without needing to change keys.
Describe the release item
Change all the admin and plugin key expressions to be in the following spaces:
@/<zenohid>/router/**@/<zenohid>/peer/**@/<zenohid>/client/**@/<zenohid>/dds/**@/<zenohid>/ros1/**@/<zenohid>/ros2/**@/<zenohid>/@ros2_pub_cache/**@/<zenohid>/@ros2_lv/**@/<zenohid>/mqtt/**@/<zenohid>/@storage/digest/**@/<zenohid>/@storage/align/**The reasons behind those changes are:
get.@namespace in the future without needing to change keys.