-
Notifications
You must be signed in to change notification settings - Fork 107
Open
Labels
Type: bugSomething isn't workingSomething isn't workinghelp wantedExtra attention is neededExtra attention is needed
Description
Describe the bug, including details regarding any error messages, version, and platform.
There are public methods to get ownership of the internal ByteBuffers, instead of having to use reflection (which, did we actually ever need it in the first place?)
There's no need to dig into our internals for accessing the ByteBuffer (which is what GetReadableBuffer reports to do). We have zero-copy APIs. They can use HasByteBuffer.getByteBuffer()+InputStream.skip() to loop through the ByteBuffers. If they want to access all the byte buffers simultaneously (as skip() will deallocate the last byte buffer, just like read() does), then they can use InputStream.mark(). If they want to take over ownership of the ByteBuffers, then they can use Detachable.detach().
Metadata
Metadata
Assignees
Labels
Type: bugSomething isn't workingSomething isn't workinghelp wantedExtra attention is neededExtra attention is needed