awslabs / awslabs/aws-sdk-rust
[request]: A synchronous API
- Dominant language
- Rust
- Stars
- 3.3k
- Forks
- 290
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 3
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue, please leave a comment
### Discussed in https://github.com/awslabs/aws-sdk-rust/discussions/80
Originally posted by **rcoh** May 13, 2021
In some cases, dealing with an async API is an unnecessary hassle. This discussion is a place to discuss the customer requirements for a sync API as well as general design considerations (eg. separate cargo feature, how does this work with streaming data, etc.)
Contributor guide
Research direction
Start with Discussion #80, which contains the customer requirements and design considerations for a synchronous API. The scope includes the API design, a possible separate Cargo feature, and streaming-data behavior; the work is not complete until those design questions are resolved and an agreed implementation plan exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100