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
We are replacing the zenoh-rest with zenoh-ts in our web application and it seems that it's not really a drop in replacement. The main motivation for replacement is to be able to use storages and get time series data (stored in cdr format). We tried a similar thing with zenoh-http but the storage queries (for example influxdb) are not completely implemented in zenoh-rest.
It is also unclear as how action clients (or service clients) for ROS2-web applications can be used with zenoh-ts. Is it possible to provide a one example snippet?
The ROS2 pub/sub seems to work perfectly.
Furthermore, is it possible to access the admin space (@) similar to zenoh-rest plugin i.e., http://localhost:8080/@/** using this plugin? We tried similar key value pair on this plugin with subscribers without any response.
Thank you.
The text was updated successfully, but these errors were encountered:
Hi there,
Thank you for providing this repository.
We are replacing the zenoh-rest with zenoh-ts in our web application and it seems that it's not really a drop in replacement. The main motivation for replacement is to be able to use storages and get time series data (stored in cdr format). We tried a similar thing with zenoh-http but the storage queries (for example influxdb) are not completely implemented in zenoh-rest.
It is also unclear as how action clients (or service clients) for ROS2-web applications can be used with zenoh-ts. Is it possible to provide a one example snippet?
The ROS2 pub/sub seems to work perfectly.
Furthermore, is it possible to access the admin space (@) similar to zenoh-rest plugin i.e., http://localhost:8080/@/** using this plugin? We tried similar key value pair on this plugin with subscribers without any response.
Thank you.
The text was updated successfully, but these errors were encountered: