Because we use it as fallback in EpollSocketChannel

> Am 20.02.2014 um 23:09 schrieb Trustin Lee <notifications@github.com>:
> 
> In transport/src/main/java/io/netty/channel/socket/nio/NioSocketChannelOutboundBuffer.java:
> 
> > +
> > +import io.netty.buffer.ByteBuf;
> > +import io.netty.buffer.ByteBufAllocator;
> > +import io.netty.buffer.ThreadLocalPooledDirectByteBuf;
> > +import io.netty.channel.AbstractChannel;
> > +import io.netty.channel.ChannelOutboundBuffer;
> > +import io.netty.util.Recycler;
> > +
> > +import java.nio.ByteBuffer;
> > +import java.util.Arrays;
> > +
> > +/**
> > + * Special {@link ChannelOutboundBuffer} implementation which allows to also access flushed {@link ByteBuffer} to
> > + * allow efficent gathering writes.
> > + */
> > +public final class NioSocketChannelOutboundBuffer extends ChannelOutboundBuffer {
> Any reason this is public while other ChannelOutboundBuffer impls are package-private?
> 
> —
> Reply to this email directly or view it on GitHub.