From 4e34d2ce6d6f2eb5f7535025948a853d4f852bc4 Mon Sep 17 00:00:00 2001 From: Brendt Lucas Date: Sun, 8 Feb 2015 12:07:46 +0000 Subject: [PATCH] Determine CompositeByteBuf implementation by using ByteBufAllocator Motivation: Currently, using a MessageAggregator in the pipeline always results in the creation of an unpooled heap CompositeByteBuf. By using the ByteBufAllocator the CompositeByteBuf will use the implementation specified by the ByteBufAllocator. Modifications: Use the ChannelHandlerContext's ByteBufAllocator to create the CompositeByteBuf for message aggregation Result: The CompositeByteBuf is now configured based on the ByteBufAllocator's settings. --- .../src/main/java/io/netty/handler/codec/MessageAggregator.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/codec/src/main/java/io/netty/handler/codec/MessageAggregator.java b/codec/src/main/java/io/netty/handler/codec/MessageAggregator.java index 6a84ca4f1e..fccdb5bf8b 100644 --- a/codec/src/main/java/io/netty/handler/codec/MessageAggregator.java +++ b/codec/src/main/java/io/netty/handler/codec/MessageAggregator.java @@ -238,7 +238,7 @@ public abstract class MessageAggregator