Skip to content

Conversation

@MikeDombo
Copy link
Contributor

Issue #, if available:

Description of changes:

  • Client can automatically create a proper client (no more IPCUtils needed) and use custom options as needed.
  • The V2 client differentiates between APIs which require a streaming response and those that do not. Those that don't, do not have a parameter to register a callback.
  • We now generate both sync and async overloads for all calls. The sync version will block on the future and throw any service errors.
  • Client has overloads with the old StreamHandler object as well as options for providing a simple callback for stream events, errors, and closing. Optionally (default is true), an executor will be used to run the stream event callback when the callback is provided as a callback. This prevents users from accidentally blocking the event loop.
  • I've updated the data model setters to return this so that we can now chain calls.
  • Streaming APIs return the handler so that the user can close the stream

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@graebm graebm merged commit 73634e0 into aws:main Jan 24, 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

Successfully merging this pull request may close these issues.

2 participants