Experiment with a map for associating objects with ByteBuffers #13656
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 map could be used to associate an object with a ByteBuffer for tunneling through APIs that only take ByteBuffer. For example, and implementation supporting transferTo could associate a particular Content.Source with an empty buffer and write that to a Sink. If the ultimate implementation of the sink takes the source and uses it, then no more writes are necessary, otherwise the content has to be written normally (i.e. as an alternative mechanism for #13631)