Scott Mitchell cf171ff525 maxBytesPerRead channel configuration ... Motiviation: The current read loops don't fascilitate reading a maximum amount of bytes. This capability is useful to have more fine grain control over how much data is injested. Modifications: - Add a setMaxBytesPerRead(int) and getMaxBytesPerRead() to ChannelConfig - Add a setMaxBytesPerIndividualRead(int) and getMaxBytesPerIndividualRead to ChannelConfig - Add methods to RecvByteBufAllocator so that a pluggable scheme can be used to control the behavior of the read loop. - Modify read loop for all transport types to respect the new RecvByteBufAllocator API Result: The ability to control how many bytes are read for each read operation/loop, and a more extensible read loop.		2015-08-05 23:59:54 -07:00
..
DefaultRxtxChannelConfig.java	maxBytesPerRead channel configuration	2015-08-05 23:59:54 -07:00
package-info.java	Rename from io.netty.transport.* to io.netty.channel.*	2013-01-14 21:34:58 +01:00
RxtxChannel.java	Apply receive timeout to commPort when using RxtxChannel. Part of [#1390]	2014-02-23 16:31:34 +01:00
RxtxChannelConfig.java	maxBytesPerRead channel configuration	2015-08-05 23:59:54 -07:00
RxtxChannelOption.java	Ensure backward-compability with 4.0	2015-04-19 13:25:42 +02:00
RxtxDeviceAddress.java	Remove 'get' prefix	2013-01-17 15:06:46 +09:00