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 issue puts together the list of items, in rough priority order, that should be completed on rmw_zenoh_cpp before Jazzy. Not all of these are strictly required, as basic functionality is already there, but having all of these will go a long way towards making rmw_zenoh_cpp something that people can actively try out.
Revisit how and when to start the zenoh router; should we do it all, should we do it automatically, or should we make the user do it?
Starting it automatically makes it more seamless, but gives the user less opportunity to configure. Need to consider the tradeoffs and what the default should be
This issue puts together the list of items, in rough priority order, that should be completed on rmw_zenoh_cpp before Jazzy. Not all of these are strictly required, as basic functionality is already there, but having all of these will go a long way towards making rmw_zenoh_cpp something that people can actively try out.
rviz2
,ros2 topic
, and other toolsrmw_take_serialized_message{_with_info}
rmw_get_gid_for_client
rmw_get_gid_for_publisher
rmw_publisher_wait_for_all_acked
wait_for_all_acked
, used in testsinit_rmw_zenoh_router
The text was updated successfully, but these errors were encountered: