MockTcpTransport
to connect asynchronously (#28203)
#33476
Merged
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.
The method
initiateChannel
onTcpTransport
is explicit in thatchannels can be connect asynchronously. All production implementations
do connect asynchronously. Only the blocking
MockTcpTransport
connects in a synchronous manner. This avoids testing some of the
blocking code in
TcpTransport
that waits on connections to complete.Additionally, it requires a more extensive method signature than
required for other transports.
This commit modifies the
MockTcpTransport
to make these connectionsasynchronously on a different thread. Additionally, it simplifies that
initiateChannel
method signature.