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
Current CRT client only supports async clients and that requires to rewrite existing sync logic. While it's often just adding .join(), other parts are more complicated to rewrite, e.g. paging logic. Sync client APIs are often much easier to use and still cover most use cases, especially for lambdas.
Use Case
Use cases:
make migration of workloads using sync clients APIs to CRT easier, avoiding rewriting sync logic
make use of easier sync client APIs when implementing new projects against CRT
AWS CRT sync HTTP client, AwsCrtHttpClient, has been released as part of 2.22.0. It's in the same CRT module as the CRT async HTTP client, aws-crt-client. Closing the issue
Comments on closed issues are hard for our team to see.
If you need more assistance, please 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.
Describe the feature
Current CRT client only supports async clients and that requires to rewrite existing sync logic. While it's often just adding .join(), other parts are more complicated to rewrite, e.g. paging logic. Sync client APIs are often much easier to use and still cover most use cases, especially for lambdas.
Use Case
Use cases:
Proposed Solution
Add sync client APIs to to CRT client.
Other Information
Also see discussion here: #2939
Acknowledgements
AWS Java SDK version used
latest
JDK version used
all currently supported
Operating System and version
all currently supported
The text was updated successfully, but these errors were encountered: