Scott Mitchell 641505a5d2 DefaultChannelConfig maxMessagesPerRead default not always set ... Motivation: ChannelMetadata has a field minMaxMessagesPerRead which can be confusing. There are also some cases where static instances are used and the default value for channel type is not being applied. Modifications: - use a default value which is set unconditionally to simplify - make sure static instances of MaxMessagesRecvByteBufAllocator are not used if the intention is that the default maxMessagesPerRead should be derived from the channel type. Result: Less confusing interfaces in ChannelMetadata and ChannelConfig. Default maxMessagesPerRead is correctly applied.		2015-11-25 15:14:07 -08:00
..
main	DefaultChannelConfig maxMessagesPerRead default not always set	2015-11-25 15:14:07 -08:00
test/java/io/netty/microbench	Add benchmark for HeapByteBuf implementations.	2015-10-29 19:38:52 +01:00