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

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

  1. HOME
  2. Java
  3. io.netty.channel.*
  4. ChannelDuplexHandler
  5. Example usage for io.netty.channel ChannelDuplexHandler subclass-usage

Introduction

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

Usage

From source file org.iotivity.cloud.base.protocols.http.HCProxyHandler.java

/**
 * This channel handler intercepts HTTP request and CoAP response
 * and translate them into CoAP request and HTTP response accordingly.
 */
public class HCProxyHandler extends ChannelDuplexHandler {

From source file org.iotivity.cloud.base.protocols.http.HttpLogHandler.java

/**
 * This class provides a set of APIs to print out logs
 * for HTTP request and response.
 */
@Sharable
public class HttpLogHandler extends ChannelDuplexHandler {

From source file org.iotivity.cloud.base.protocols.proxy.CoapHttpProxyHandler.java

@Sharable
public class CoapHttpProxyHandler extends ChannelDuplexHandler {

    // Proxy converts http request to coaprequest and coapresponse to
    // httpresponse
    private SessionManager sessionManager = null;

From source file org.iotivity.cloud.ciserver.protocols.CoapAuthHandler.java

@Sharable
public class CoapAuthHandler extends ChannelDuplexHandler {

    private static final AttributeKey<ChannelHandlerContext> keyAuthClient = AttributeKey.newInstance("authCtx");

    private class AccountHandler extends SimpleChannelInboundHandler<CoapResponse> {

From source file org.iotivity.cloud.ciserver.protocols.CoapRelayHandler.java

/**
 *
 * This class is relay handler relating Cloud Interface
 *
 */
@Sharable

From source file org.iotivity.cloud.util.CoapLogHandler.java

/**
 *
 * This class provides a set of APIs to print out logs for CoAP request and
 * response.
 *
 */

From source file org.jmqtt.broker.handler.AutoFlushHandler.java

/**
 * Auto-flush data on channel after a read timeout.
 * It's inspired by IdleStateHandler but it's specialized version, just flushing data after
 * no read is done on the channel after a period. It's used to avoid aggressively flushing from
 * the ProtocolProcessor.
 */

From source file org.jmqtt.broker.handler.IdleTimeoutHandler.java

@Sharable
public class IdleTimeoutHandler extends ChannelDuplexHandler {
    @Override
    public void userEventTriggered(ChannelHandlerContext ctx, Object evt) throws Exception {
        if (evt instanceof IdleStateEvent) {
            IdleState e = ((IdleStateEvent) evt).state();

From source file org.jmqtt.broker.metrics.BytesMetricsHandler.java

public class BytesMetricsHandler extends ChannelDuplexHandler {

    private static final AttributeKey<BytesMetrics> ATTR_KEY_METRICS = AttributeKey.valueOf("BytesMetrics");

    private BytesMetricsCollector collector;

From source file org.jmqtt.broker.metrics.MessageMetricsHandler.java

public class MessageMetricsHandler extends ChannelDuplexHandler {

    private static final AttributeKey<MessageMetrics> ATTR_KEY_METRICS = AttributeKey.valueOf("MessageMetrics");

    private MessageMetricsCollector collector;