Norman Maurer d9a6cf341c Remove support for marking reader and writerIndex in ByteBuf to reduce overhead and complexity. (#8636) ... Motivation: ByteBuf supports “marker indexes”. The intended use case for these is if a speculative operation (e.g. decode) is in process the user can “mark” and interface and refer to it later if the operation isn’t successful (e.g. not enough data). However this is rarely used in practice, requires extra memory to maintain, and introduces complexity in the state management for derived/pooled buffer initialization, resizing, and other operations which may modify reader/writer indexes. Modifications: Remove support for marking and adjust testcases / code. Result: Fixes https://github.com/netty/netty/issues/8535.		2018-12-11 14:00:49 +01:00
..
main/java/io/netty/buffer	Remove support for marking reader and writerIndex in ByteBuf to reduce overhead and complexity. (#8636)	2018-12-11 14:00:49 +01:00
test/java/io/netty/buffer	Remove support for marking reader and writerIndex in ByteBuf to reduce overhead and complexity. (#8636)	2018-12-11 14:00:49 +01:00