Derek Troy-West 8796fd3025 Change AggregatedFullHttpMessage to contain a content ByteBuf ... Motivation: Other implementations of FullHttpMessage allow .toString to be called after the Message has been released This brings AggregatedFullHttpMessage into line with those impls. Modifications: - Changed AggregatedFullHttpMessage to no longer be a sub-class of DefaultByteBufHolder - Changes AggregatedFullHttpMessage to implement ByteBufHolder - Hold the content buffer internally to AggregatedFullHttpMessage - Implement the required content() and release() methods that were missing - Do not check refcnt when accessing content() (similar to DefaultFullHttpMessage) Result: A released AggregatedFullHttpMessage can have .toString called without throwing an exception		2015-04-16 17:28:39 +02:00
..
src	Change AggregatedFullHttpMessage to contain a content ByteBuf	2015-04-16 17:28:39 +02:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2015-03-03 08:30:59 -05:00