Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to use tokio instead of async-std #11

Open
PLeVasseur opened this issue May 30, 2024 · 2 comments
Open

Update to use tokio instead of async-std #11

PLeVasseur opened this issue May 30, 2024 · 2 comments

Comments

@PLeVasseur
Copy link
Contributor

Since Zenoh has transitioned as of its 0.11 release to tokio from async-std, we will do the same.

cc @evshary

@evshary
Copy link

evshary commented Aug 14, 2024

Now in zenoh 1.0 alpha.6, all the plugins are using tokio. Just FYI
eclipse-zenoh/zenoh#1257

@PLeVasseur
Copy link
Contributor Author

Gotcha. Thanks for the heads up! 🙂

PLeVasseur added a commit that referenced this issue Nov 14, 2024
Main content:

* Convert up-streamer from async-std to tokio
* Update tests to tokio from async-std
* Ensure examples work again:
  * me_service <-> ue_client
  * ue_service <-> me_client
  * ue_publisher -> me_subscriber
  * me_publisher -> ue_subscriber

Useful improvements:

* Remove 'unstable' and 'internal' features of Zenoh now that no longer needed.
* Modify build to allow optionally building with Zenoh and/or vsomeip. If building with both, reference streamers that use them both are then built.
* Move optional dependecies' version declaration into workspace Cargo.toml, flag as optional in each package.

Implements #11
Implements #29
Implements #53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

2 participants