Allow to access memoryAddress of wrapped ByteBuf for ReadOnlyByteBuf
Motivation: We should allow to access the memoryAddress of the wrapped ByteBuf when using ReadOnlyByteBuf for peformance reasons. If a user act on a memoryAddress its his responsible anyway to do nothing "stupid". Modifications: Delegate to wrapped ByteBuf. Result: Less performance overhead for various operations and also when writing to a native transport (which needs the memoryAddress).
This commit is contained in:
parent
629b83e0a5
commit
7922757575
@ -103,12 +103,12 @@ public class ReadOnlyByteBuf extends AbstractDerivedByteBuf {
|
|||||||
|
|
||||||
@Override
|
@Override
|
||||||
public boolean hasMemoryAddress() {
|
public boolean hasMemoryAddress() {
|
||||||
return false;
|
return unwrap().hasMemoryAddress();
|
||||||
}
|
}
|
||||||
|
|
||||||
@Override
|
@Override
|
||||||
public long memoryAddress() {
|
public long memoryAddress() {
|
||||||
throw new ReadOnlyBufferException();
|
return unwrap().memoryAddress();
|
||||||
}
|
}
|
||||||
|
|
||||||
@Override
|
@Override
|
||||||
|
Loading…
Reference in New Issue
Block a user