Class BinaryMemcacheResponseEncoder
java.lang.Object
io.netty.channel.ChannelHandlerAdapter
io.netty.channel.ChannelOutboundHandlerAdapter
io.netty.handler.codec.MessageToMessageEncoder<Object>
io.netty.handler.codec.memcache.AbstractMemcacheObjectEncoder<BinaryMemcacheResponse>
io.netty.handler.codec.memcache.binary.AbstractBinaryMemcacheEncoder<BinaryMemcacheResponse>
io.netty.handler.codec.memcache.binary.BinaryMemcacheResponseEncoder
- All Implemented Interfaces:
ChannelHandler, ChannelOutboundHandler
@UnstableApi
public class BinaryMemcacheResponseEncoder
extends AbstractBinaryMemcacheEncoder<BinaryMemcacheResponse>
The encoder which takes care of encoding the response headers.
-
Nested Class Summary
Nested classes/interfaces inherited from interface ChannelHandler
ChannelHandler.SharableModifier and TypeInterfaceDescriptionstatic @interfaceIndicates that the same instance of the annotatedChannelHandlercan be added to one or moreChannelPipelines multiple times without a race condition. -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionprotected voidencodeHeader(ByteBuf buf, BinaryMemcacheResponse msg) Encode the header.Methods inherited from class AbstractBinaryMemcacheEncoder
encodeMessageModifier and TypeMethodDescriptionprotected ByteBufTake the givenMemcacheMessageand encode it into a writableByteBuf.Methods inherited from class AbstractMemcacheObjectEncoder
acceptOutboundMessage, encodeModifier and TypeMethodDescriptionbooleanReturnstrueif the given message should be handled.protected voidencode(ChannelHandlerContext ctx, Object msg, List<Object> out) Encode from one message to an other.Methods inherited from class MessageToMessageEncoder
writeModifier and TypeMethodDescriptionvoidwrite(ChannelHandlerContext ctx, Object msg, ChannelPromise promise) CallsChannelOutboundInvoker.write(Object, ChannelPromise)to forward to the nextChannelOutboundHandlerin theChannelPipeline.Methods inherited from class ChannelOutboundHandlerAdapter
bind, close, connect, deregister, disconnect, flush, readModifier and TypeMethodDescriptionvoidbind(ChannelHandlerContext ctx, SocketAddress localAddress, ChannelPromise promise) CallsChannelOutboundInvoker.bind(SocketAddress, ChannelPromise)to forward to the nextChannelOutboundHandlerin theChannelPipeline.voidclose(ChannelHandlerContext ctx, ChannelPromise promise) CallsChannelOutboundInvoker.close(ChannelPromise)to forward to the nextChannelOutboundHandlerin theChannelPipeline.voidconnect(ChannelHandlerContext ctx, SocketAddress remoteAddress, SocketAddress localAddress, ChannelPromise promise) CallsChannelOutboundInvoker.connect(SocketAddress, SocketAddress, ChannelPromise)to forward to the nextChannelOutboundHandlerin theChannelPipeline.voidderegister(ChannelHandlerContext ctx, ChannelPromise promise) CallsChannelOutboundInvoker.deregister(ChannelPromise)to forward to the nextChannelOutboundHandlerin theChannelPipeline.voiddisconnect(ChannelHandlerContext ctx, ChannelPromise promise) CallsChannelOutboundInvoker.disconnect(ChannelPromise)to forward to the nextChannelOutboundHandlerin theChannelPipeline.voidCallsChannelHandlerContext.flush()to forward to the nextChannelOutboundHandlerin theChannelPipeline.voidCallsChannelHandlerContext.read()to forward to the nextChannelOutboundHandlerin theChannelPipeline.Methods inherited from class ChannelHandlerAdapter
ensureNotSharable, exceptionCaught, handlerAdded, handlerRemoved, isSharableModifier and TypeMethodDescriptionprotected voidvoidexceptionCaught(ChannelHandlerContext ctx, Throwable cause) Deprecated.voidDo nothing by default, sub-classes may override this method.voidDo nothing by default, sub-classes may override this method.booleanReturntrueif the implementation isChannelHandler.Sharableand so can be added to differentChannelPipelines.
-
Constructor Details
-
BinaryMemcacheResponseEncoder
public BinaryMemcacheResponseEncoder()
-
-
Method Details
-
encodeHeader
Description copied from class:AbstractBinaryMemcacheEncoderEncode the header. This methods needs to be implemented by a sub class because the header is different for both requests and responses.- Specified by:
encodeHeaderin classAbstractBinaryMemcacheEncoder<BinaryMemcacheResponse>- Parameters:
buf- theByteBufto write into.msg- the message to encode.
-
ChannelInboundHandler