Remove AsyncClientConnect and AsyncSecureClientConnect in favor of async constructors #1541
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the second PR associated with #1532, removing the intermediate
AsyncClientConnect
object in favor ofasync
functions to construct theAsyncClient
, as discussed on the issue.I also removed
AsyncSecureClientConnect
and make similar changes toAsyncDnssecClient
as they were also based onAsyncClientConnect
/AsyncClient
.There should be very little to no changes in usage for users, and the tests still all pass on my machine without having had to make any change to them.