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

Migrate from Tokio, Hyper and Axum #205

Open
rvolosatovs opened this issue Jun 21, 2022 · 0 comments
Open

Migrate from Tokio, Hyper and Axum #205

rvolosatovs opened this issue Jun 21, 2022 · 0 comments
Assignees

Comments

@rvolosatovs
Copy link
Member

Currently we rely on two different async infrastructures - tokio and async-std, which complicates usage (e.g. we sometimes need a compatibility layer) and increases our compilation times.

We have to rely on cap-async-std (https://docs.rs/cap-async-std/latest/cap_async_std/index.html), since we want to be able to run Drawbridge within as a WASI executable, therefore we should completely switch to async-std ecosystem.

We need:

@rvolosatovs rvolosatovs self-assigned this Jun 21, 2022
@dpal dpal moved this to New in Profian Board Nov 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant