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

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

Introduction

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

Usage

From source file com.chenyang.proxy.http.HttpRelayHandler.java

public class HttpRelayHandler extends ChannelInboundHandlerAdapter {

    private static Logger logger = LoggerFactory.getLogger(HttpRelayHandler.class);
    public static final String HANDLER_NAME = "apnproxy.relay";

    private final Channel relayChannel;

From source file com.chenyang.proxy.http.HttpRemoteForwardHandler.java

public class HttpRemoteForwardHandler extends ChannelInboundHandlerAdapter {

    private static Logger logger = LoggerFactory.getLogger(HttpRemoteForwardHandler.class);

    public static final String HANDLER_NAME = "apnproxy.remote.forward";

From source file com.chenyang.proxy.http.HttpSchemaHandler.java

@ChannelHandler.Sharable
public class HttpSchemaHandler extends ChannelInboundHandlerAdapter {

    private static Logger logger = LoggerFactory.getLogger(HttpSchemaHandler.class);
    public static final String HANDLER_NAME = "apnproxy.schema";

From source file com.chenyang.proxy.http.HttpUserAgentForwardHandler.java

public class HttpUserAgentForwardHandler extends ChannelInboundHandlerAdapter
        implements RemoteChannelInactiveCallback {

    private static Logger logger = LoggerFactory.getLogger(HttpUserAgentForwardHandler.class);
    public static final String HANDLER_NAME = "apnproxy.useragent.forward";

From source file com.chenyang.proxy.http.HttpUserAgentTunnelHandler.java

public class HttpUserAgentTunnelHandler extends ChannelInboundHandlerAdapter {

    public static final String HANDLER_NAME = "apnproxy.useragent.tunnel";
    private static Logger logger = LoggerFactory.getLogger(HttpUserAgentTunnelHandler.class);

    @Override

From source file com.cloudhopper.smpp.channel.SmppClientConnector.java

/**
 * The default handler used just during a "connect" for a Channel when attempting
 * to bind into an SMSC.  The reason is that some handler must be added to create
 * a channel and then replaced before the actual "bind" is attempted.  This
 * handler basically does nothing.  Until a "bind" request is received by the SMSC,
 * nothing should actually be received so its safe to have a handler that does

From source file com.cloudhopper.smpp.channel.SmppServerConnector.java

/**
 * Channel handler for server SMPP sessions.
 * 
 * @author joelauer (twitter: @jjlauer or <a href="http://twitter.com/jjlauer" target=window>http://twitter.com/jjlauer</a>)
 */
@Sharable

From source file com.cloudhopper.smpp.channel.SmppSessionThreadRenamer.java

/**
 * Channel handler responsible for renaming the current thread, passing the
 * event upstream, then renaming the thread back after its done processing. This
 * handler should be the first one in the pipeline to make sure all handlers
 * after it have the correct thread name for proper logging.
 *

From source file com.cmz.sctp.SctpEchoClientHandler.java

/**
 * Handler implementation for the SCTP echo client.  It initiates the ping-pong
 * traffic between the echo client and server by sending the first message to
 * the server.
 */
public class SctpEchoClientHandler extends ChannelInboundHandlerAdapter {

From source file com.cmz.sctp.SctpEchoServerHandler.java

/**
 * Handler implementation for the SCTP echo server.
 */
@Sharable
public class SctpEchoServerHandler extends ChannelInboundHandlerAdapter {