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
in ROS2's concept, can it has the node with the same name, expecially considering the builtin client service (eg. list_parameters, get_parameters, set_parameters ...), for this will make the two node fully connected by these services and clients.
The text was updated successfully, but these errors were encountered:
The current unwritten assumption is that node names need to be unique. There's a long standing task to make a design document on this topic with details on how to enforce the node name uniqueness (given that discovery is by default distributed without a master).
We're talked about it several times off-line, but it's explicitly mentioned as a design issue on this issue about parameter refactoring: ros2/ros2#432
I'll close this for now as it's more of a question, but I made this issue to track the need for the design document about this: #187
in ROS2's concept, can it has the node with the same name, expecially considering the builtin client service (eg. list_parameters, get_parameters, set_parameters ...), for this will make the two node fully connected by these services and clients.
The text was updated successfully, but these errors were encountered: