Example usage for io.netty.channel SimpleChannelInboundHandler subclass-usage

List of usage examples for io.netty.channel SimpleChannelInboundHandler subclass-usage

Introduction

In this page you can find the example usage for io.netty.channel SimpleChannelInboundHandler subclass-usage.

Usage

From source file com.corundumstudio.socketio.handler.InPacketHandler.java

@Sharable
public class InPacketHandler extends SimpleChannelInboundHandler<PacketsMessage> {

    private final Logger log = LoggerFactory.getLogger(getClass());

    private final PacketListener packetListener;

From source file com.corundumstudio.socketio.handler.PacketHandler.java

@Sharable
public class PacketHandler extends SimpleChannelInboundHandler<PacketsMessage> {

    private final Logger log = LoggerFactory.getLogger(getClass());

    private final PacketListener packetListener;

From source file com.couchbase.client.core.endpoint.binary.BinaryAuthHandler.java

/**
 * A SASL Client which communicates through the memcache binary protocol.
 *
 * @author Michael Nitschinger
 * @since 1.0
 */

From source file com.couchbase.client.core.endpoint.binary.BinarySaslClient.java

/**
 * A SASL Client which communicates through the memcache binary protocol.
 *
 * @author Michael Nitschinger
 * @since 1.0
 */

From source file com.couchbase.client.core.endpoint.dcp.DCPConnectionHandler.java

/**
 * DCP connection handler makes sure that all channels have DCP connection initialized.
 *
 * @author Sergey Avseyev
 * @since 1.2.6
 */

From source file com.couchbase.client.core.endpoint.kv.KeyValueAuthHandler.java

/**
 * A SASL Client which communicates through the memcache binary protocol.
 *
 * @author Michael Nitschinger
 * @since 1.0
 */

From source file com.couchbase.client.core.endpoint.kv.KeyValueFeatureHandler.java

/**
 * This handler negotiates the enabled features through the HELLO command.
 *
 * Like the SASL auth handler, this handler intercepts the original connect process to properly negotiate the
 * supported features with the server. Once the features are negotiated they are sent through custom events up the
 * pipeline and the handler removes itself.

From source file com.couchbase.client.io.QueryDecoder.java

/**
 * Decode incoming {@link HttpObject}s and complete
 * {@link com.couchbase.client.internal.HttpFuture}s.
 *
 * Every response that arrives from the server, comes into this decoder.
 * Once the HTTP header is received, a new operation is picked from the queue and the

From source file com.creamsugardonut.HttpStaticFileServerHandler2.java

/**
 * Http static server via zero copy which reduces overhead of copying kernel buffer to memory.
 */
public class HttpStaticFileServerHandler2 extends SimpleChannelInboundHandler<HttpRequest> {

    @Override

From source file com.crm.provisioning.thread.osa.CallbackServerHandler.java

public class CallbackServerHandler extends SimpleChannelInboundHandler<Object> {
    private CallbackServer callbackServer = null;
    private DispatcherThread dispatcher = null;

    private HttpRequest request = null;
    private Date requestDate = null;