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

[request]: Provide a async API for different async runtime crates and also a sync API #506

Closed
jmklix opened this issue Apr 6, 2022 Discussed in #79 · 2 comments
Closed
Labels
feature-request A feature should be added or improved.

Comments

@jmklix
Copy link
Member

jmklix commented Apr 6, 2022

Discussed in #79

Originally posted by howard-quantrend May 12, 2021
Maybe the sdk could support both popular async runtimes, tokio and async-std using feature flags? In my case, our project only uses the async-std crate, so we need to rewrite the necessary parts of the Rusoto crate ourselves using async-std runtime. It will be great if the aws-sdk-rust supports both runtimes using feature flags, and even better if it provides a blocking sync API too, to support different kind of projects. Actually, this is what the MongoDB rust driver does. Thanks.

You can actually use async-std today by providing your own implementation of the HttpService trait.

If there's enough customer interest, we may consider providing first-class support, but it's worth noting that the workaround exists today. In the current SDK, you would still need to run a 1-threaded Tokio runtime to support retries (which have not yet been made runtime agnostic, although they are planned to be)

@jmklix jmklix added the feature-request A feature should be added or improved. label Apr 6, 2022
@jdisanti
Copy link
Contributor

jdisanti commented Apr 7, 2022

Multiple async runtime support is tracked in #52. Sync API is tracked in #505

@jdisanti jdisanti closed this as completed Apr 7, 2022
@github-actions
Copy link

github-actions bot commented Apr 7, 2022

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

2 participants