Added AsyncResponseTransformer.toBlockingInputStream. #3562
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 allows streaming operation responses to be read as if they're an InputStream.
Example usage:
Other changes made to support this change:
InputStreamSubscriber
, aSubscriber<ByteBuffer>
that extendsInputStream
. It allows subscribing to a publisher and then performing blocking reads against it. This is used byAsyncResponseTransformer
.ByteBufferStoringSubscriber
to supportblockingTransferTo(ByteBuffer)
. It's liketransferTo(ByteBuffer)
, except that it will block the caller until at least one byte of data is available to be read. This is used byInputStreamSubscriber
.ResponseInputStream
to store non-abortable streams. This is used byAsyncResponseTransformer
.