Examples of ChannelPipeline

com.facebook.presto.jdbc.internal.netty.channel.ChannelPipeline
sun.com/blueprints/corej2eepatterns/Patterns/InterceptingFilter.html">Intercepting Filter pattern to give a user full control over how an event is handled and how the {@link ChannelHandler}s in the pipeline interact with each other.
Creation of a pipeline
For each new channel, a new pipeline must be created and attached to the channel. Once attached, the coupling between the channel and the pipeline is permanent; the channel cannot attach another pipeline to it nor detach the current pipeline from it.
The recommended way to create a new pipeline is to use the helper methods in {@link Channels} rather than calling an individual implementation'sconstructor:
```
 import static com.facebook.presto.jdbc.internal.netty.channel. {@link Channels}.*; {@link ChannelPipeline} pipeline = pipeline(); // same with Channels.pipeline()
```
How an event flows in a pipeline
The following diagram describes how {@link ChannelEvent}s are processed by {@link ChannelHandler}s in a {@link ChannelPipeline} typically.A {@link ChannelEvent} can be handled by either a {@link ChannelUpstreamHandler}or a {@link ChannelDownstreamHandler} and be forwarded to the closesthandler by calling {@link ChannelHandlerContext#sendUpstream(ChannelEvent)}or {@link ChannelHandlerContext#sendDownstream(ChannelEvent)}. The meaning of the event is interpreted somewhat differently depending on whether it is going upstream or going downstream. Please refer to {@link ChannelEvent} formore information.
```
 I/O Request via  {@link Channel} or{@link ChannelHandlerContext}| +----------------------------------------+---------------+ |                  ChannelPipeline       |               | |                                       \|/              | |  +----------------------+  +-----------+------------+  | |  | Upstream Handler  N  |  | Downstream Handler  1  |  | |  +----------+-----------+  +-----------+------------+  | |            /|\                         |               | |             |                         \|/              | |  +----------+-----------+  +-----------+------------+  | |  | Upstream Handler N-1 |  | Downstream Handler  2  |  | |  +----------+-----------+  +-----------+------------+  | |            /|\                         .               | |             .                          .               | |     [ sendUpstream() ]        [ sendDownstream() ]     | |     [ + INBOUND data ]        [ + OUTBOUND data  ]     | |             .                          .               | |             .                         \|/              | |  +----------+-----------+  +-----------+------------+  | |  | Upstream Handler  2  |  | Downstream Handler M-1 |  | |  +----------+-----------+  +-----------+------------+  | |            /|\                         |               | |             |                         \|/              | |  +----------+-----------+  +-----------+------------+  | |  | Upstream Handler  1  |  | Downstream Handler  M  |  | |  +----------+-----------+  +-----------+------------+  | |            /|\                         |               | +-------------+--------------------------+---------------+ |                         \|/ +-------------+--------------------------+---------------+ |             |                          |               | |     [ Socket.read() ]          [ Socket.write() ]      | |                                                        | |  Netty Internal I/O Threads (Transport Implementation) | +--------------------------------------------------------+ 
```
An upstream event is handled by the upstream handlers in the bottom-up direction as shown on the left side of the diagram. An upstream handler usually handles the inbound data generated by the I/O thread on the bottom of the diagram. The inbound data is often read from a remote peer via the actual input operation such as {@link InputStream#read(byte[])}. If an upstream event goes beyond the top upstream handler, it is discarded silently.
A downstream event is handled by the downstream handler in the top-down direction as shown on the right side of the diagram. A downstream handler usually generates or transforms the outbound traffic such as write requests. If a downstream event goes beyond the bottom downstream handler, it is handled by an I/O thread associated with the {@link Channel}. The I/O thread often performs the actual output operation such as {@link OutputStream#write(byte[])}.
For example, let us assume that we created the following pipeline:
```
 {@link ChannelPipeline} p = {@link Channels}.pipeline(); p.addLast("1", new UpstreamHandlerA()); p.addLast("2", new UpstreamHandlerB()); p.addLast("3", new DownstreamHandlerA()); p.addLast("4", new DownstreamHandlerB()); p.addLast("5", new UpstreamHandlerX()); 
```
In the example above, the class whose name starts with {@code Upstream} meansit is an upstream handler. The class whose name starts with {@code Downstream} means it is a downstream handler.
In the given example configuration, the handler evaluation order is 1, 2, 3, 4, 5 when an event goes upstream. When an event goes downstream, the order is 5, 4, 3, 2, 1. On top of this principle, {@link ChannelPipeline} skipsthe evaluation of certain handlers to shorten the stack depth:
- 3 and 4 don't implement {@link ChannelUpstreamHandler}, and therefore the actual evaluation order of an upstream event will be: 1, 2, and 5.
- 1, 2, and 5 don't implement {@link ChannelDownstreamHandler}, and therefore the actual evaluation order of a downstream event will be: 4 and 3.
- If 5 extended {@link SimpleChannelHandler} which implements both{@link ChannelUpstreamHandler} and {@link ChannelDownstreamHandler}, the evaluation order of an upstream and a downstream event could be 125 and 543 respectively.
Building a pipeline

A user is supposed to have one or more {@link ChannelHandler}s in a pipeline to receive I/O events (e.g. read) and to request I/O operations (e.g. write and close). For example, a typical server will have the following handlers in each channel's pipeline, but your mileage may vary depending on the complexity and characteristics of the protocol and business logic:
1. Protocol Decoder - translates binary data (e.g. {@link ChannelBuffer}) into a Java object.
2. Protocol Encoder - translates a Java object into binary data.
3. {@link ExecutionHandler} - applies a thread model.
4. Business Logic Handler - performs the actual business logic (e.g. database access).
and it could be represented as shown in the following example:
```
 {@link ChannelPipeline} pipeline = {@link Channels#pipeline() Channels.pipeline()}; pipeline.addLast("decoder", new MyProtocolDecoder()); pipeline.addLast("encoder", new MyProtocolEncoder()); pipeline.addLast("executor", new  {@link ExecutionHandler}( new  {@link OrderedMemoryAwareThreadPoolExecutor}(16, 1048576, 1048576))); pipeline.addLast("handler", new MyBusinessLogicHandler()); 
```
Thread safety

A {@link ChannelHandler} can be added or removed at any time because a{@link ChannelPipeline} is thread safe. For example, you can insert a{@link SslHandler} when sensitive information is about to be exchanged,and remove it after the exchange.
Pitfall

Due to the internal implementation detail of the current default {@link ChannelPipeline}, the following code does not work as expected if FirstHandler is the last handler in the pipeline:
```
 public class FirstHandler extends  {@link SimpleChannelUpstreamHandler} {{@code @Override}public void messageReceived( {@link ChannelHandlerContext} ctx, {@link MessageEvent} e) {// Remove this handler from the pipeline, ctx.getPipeline().remove(this); // And let SecondHandler handle the current event. ctx.getPipeline().addLast("2nd", new SecondHandler()); ctx.sendUpstream(e); } } 
```
To implement the expected behavior, you have to add SecondHandler before the removal or make sure there is at least one more handler between FirstHandler and SecondHandler. @apiviz.landmark @apiviz.composedOf com.facebook.presto.jdbc.internal.netty.channel.ChannelHandlerContext @apiviz.owns com.facebook.presto.jdbc.internal.netty.channel.ChannelHandler @apiviz.uses com.facebook.presto.jdbc.internal.netty.channel.ChannelSink - - sends events downstream
io.netty.channel.ChannelPipeline
sun.com/blueprints/corej2eepatterns/Patterns/InterceptingFilter.html">Intercepting Filter pattern to give a user full control over how an event is handled and how the {@link ChannelHandler}s in the pipeline interact with each other.
Creation of a pipeline
For each new channel, a new pipeline iscreated and attached to the channel. Once attached, the coupling between the channel and the pipeline is permanent; the channel cannot attach another pipeline to it nor detach the current pipeline from it. All of this is handled for you and you not need to take care of this.

How an event flows in a pipeline
The following diagram describes how I/O is processed by {@link ChannelHandler}s in a {@link ChannelPipeline} typically.A I/O-operation can be handled by either a {@link ChannelInboundHandler}or a {@link ChannelOutboundHandler} and be forwarded to the closesthandler by calling either one of the methods defined in the {@link ChannelInboundInvoker} interface for inbound I/O or by oneof the methods defined in the {@link ChannelOutboundInvoker} interfacefor outbound I/O. {@link ChannelPipeline} extends both of them.
```
 I/O Request via  {@link Channel} or{@link ChannelHandlerContext}| +----------------------------------------------------+-----------------+ |                           ChannelPipeline          |                 | |                                                   \|/                | |    +----------------------+            +-----------+------------+    | |    | Inbound Handler  N   |            | Outbound Handler  1    |    | |    +----------+-----------+            +-----------+------------+    | |              /|\                                   |                 | |               |                                   \|/                | |    +----------+-----------+            +-----------+------------+    | |    | Inbound Handler N-1  |            |   Outbound Handler  2  |    | |    +----------+-----------+            +-----------+------------+    | |              /|\                                   .                 | |               .                                    .                 | | [ {@link ChannelInboundInvoker}]   [ {@link ChannelOutboundInvoker}()] | |        [ method call]                    [method call]               | |               .                                    .                 | |               .                                   \|/                | |    +----------+-----------+            +-----------+------------+    | |    | Inbound Handler  2   |            | Outbound Handler M-1   |    | |    +----------+-----------+            +-----------+------------+    | |              /|\                                   |                 | |               |                                   \|/                | |    +----------+-----------+            +-----------+------------+    | |    | Inbound Handler  1   |            | Outbound Handler  M    |    | |    +----------+-----------+            +-----------+------------+    | |              /|\                                   |                 | +---------------+------------------------------------+-----------------+ |                                   \|/ +---------------+------------------------------------+-----------------+ |               |                                    |                 | |       [ Socket.read() ]                     [ Socket.write() ]       | |                                                                      | |  Netty Internal I/O Threads (Transport Implementation)               | +----------------------------------------------------------------------+ 
```
An upstream event is handled by the upstream handlers in the bottom-up direction as shown on the left side of the diagram. An upstream handler usually handles the inbound data generated by the I/O thread on the bottom of the diagram. The inbound data is often read from a remote peer via the actual input operation such as {@link InputStream#read(byte[])}. If an upstream event goes beyond the top upstream handler, it is discarded silently.
A downstream event is handled by the downstream handler in the top-down direction as shown on the right side of the diagram. A downstream handler usually generates or transforms the outbound traffic such as write requests. If a downstream event goes beyond the bottom downstream handler, it is handled by an I/O thread associated with the {@link Channel}. The I/O thread often performs the actual output operation such as {@link OutputStream#write(byte[])}.
For example, let us assume that we created the following pipeline:
```
 {@link ChannelPipeline} p = ...;p.addLast("1", new InboundHandlerA()); p.addLast("2", new InboundHandlerB()); p.addLast("3", new OutboundHandlerA()); p.addLast("4", new OutboundHandlerB()); p.addLast("5", new InboundOutboundHandlerX()); 
```
In the example above, the class whose name starts with {@code Upstream} meansit is an upstream handler. The class whose name starts with {@code Downstream} means it is a downstream handler.
In the given example configuration, the handler evaluation order is 1, 2, 3, 4, 5 when an event goes upstream. When an event goes downstream, the order is 5, 4, 3, 2, 1. On top of this principle, {@link ChannelPipeline} skipsthe evaluation of certain handlers to shorten the stack depth:
- 3 and 4 don't implement {@link ChannelInboundHandler}, and therefore the actual evaluation order of an upstream event will be: 1, 2, and 5.
- 1, 2, and 5 don't implement {@link ChannelOutboundHandler}, and therefore the actual evaluation order of a downstream event will be: 4 and 3.
- If 5 implements both {@link ChannelInboundHandler} and {@link ChannelOutboundHandler}, the evaluation order of an upstream and a downstream event could be 125 and 543 respectively.
Building a pipeline

A user is supposed to have one or more {@link ChannelHandler}s in a pipeline to receive I/O events (e.g. read) and to request I/O operations (e.g. write and close). For example, a typical server will have the following handlers in each channel's pipeline, but your mileage may vary depending on the complexity and characteristics of the protocol and business logic:
1. Protocol Decoder - translates binary data (e.g. {@link ByteBuf}) into a Java object.
2. Protocol Encoder - translates a Java object into binary data.
3. ExecutionHandler - applies a thread model.
4. Business Logic Handler - performs the actual business logic (e.g. database access).
and it could be represented as shown in the following example:
```
 {@link ChannelPipeline} pipeline = ...;pipeline.addLast("decoder", new MyProtocolDecoder()); pipeline.addLast("encoder", new MyProtocolEncoder()); pipeline.addLast("executor", new ExecutionHandler(...)); pipeline.addLast("handler", new MyBusinessLogicHandler()); 
```
Thread safety

A {@link ChannelHandler} can be added or removed at any time because a{@link ChannelPipeline} is thread safe. For example, you can insert anencryption handler when sensitive information is about to be exchanged, and remove it after the exchange.
net.gleamynode.netty.channel.ChannelPipeline
@author The Netty Project (netty@googlegroups.com) @author Trustin Lee (trustin@gmail.com) @version $Rev: 479 $, $Date: 2008-07-04 16:04:47 +0900 (Fri, 04 Jul 2008) $ @apiviz.landmark @apiviz.composedOf net.gleamynode.netty.channel.ChannelHandlerContext @apiviz.owns net.gleamynode.netty.channel.ChannelHandler @apiviz.uses net.gleamynode.netty.channel.ChannelSink - - sends downstream events
net.minecraft.util.io.netty.channel.ChannelPipeline
org.elasticsearch.common.netty.channel.ChannelPipeline
org.jboss.netty.channel.ChannelPipeline
sun.com/blueprints/corej2eepatterns/Patterns/InterceptingFilter.html">Intercepting Filter pattern to give a user full control over how an event is handled and how the {@link ChannelHandler}s in the pipeline interact with each other.
Creation of a pipeline
For each new channel, a new pipeline must be created and attached to the channel. Once attached, the coupling between the channel and the pipeline is permanent; the channel cannot attach another pipeline to it nor detach the current pipeline from it.
The recommended way to create a new pipeline is to use the helper methods in {@link Channels} rather than calling an individual implementation'sconstructor:
```
 import static org.jboss.netty.channel. {@link Channels}.*; {@link ChannelPipeline} pipeline = pipeline(); // same with Channels.pipeline()
```
How an event flows in a pipeline
The following diagram describes how {@link ChannelEvent}s are processed by {@link ChannelHandler}s in a {@link ChannelPipeline} typically.A {@link ChannelEvent} can be handled by either a {@link ChannelUpstreamHandler}or a {@link ChannelDownstreamHandler} and be forwarded to the closesthandler by calling {@link ChannelHandlerContext#sendUpstream(ChannelEvent)}or {@link ChannelHandlerContext#sendDownstream(ChannelEvent)}. The meaning of the event is interpreted somewhat differently depending on whether it is going upstream or going downstream. Please refer to {@link ChannelEvent} formore information.
```
 I/O Request via  {@link Channel} or{@link ChannelHandlerContext}| +----------------------------------------+---------------+ |                  ChannelPipeline       |               | |                                       \|/              | |  +----------------------+  +-----------+------------+  | |  | Upstream Handler  N  |  | Downstream Handler  1  |  | |  +----------+-----------+  +-----------+------------+  | |            /|\                         |               | |             |                         \|/              | |  +----------+-----------+  +-----------+------------+  | |  | Upstream Handler N-1 |  | Downstream Handler  2  |  | |  +----------+-----------+  +-----------+------------+  | |            /|\                         .               | |             .                          .               | |     [ sendUpstream() ]        [ sendDownstream() ]     | |     [ + INBOUND data ]        [ + OUTBOUND data  ]     | |             .                          .               | |             .                         \|/              | |  +----------+-----------+  +-----------+------------+  | |  | Upstream Handler  2  |  | Downstream Handler M-1 |  | |  +----------+-----------+  +-----------+------------+  | |            /|\                         |               | |             |                         \|/              | |  +----------+-----------+  +-----------+------------+  | |  | Upstream Handler  1  |  | Downstream Handler  M  |  | |  +----------+-----------+  +-----------+------------+  | |            /|\                         |               | +-------------+--------------------------+---------------+ |                         \|/ +-------------+--------------------------+---------------+ |             |                          |               | |     [ Socket.read() ]          [ Socket.write() ]      | |                                                        | |  Netty Internal I/O Threads (Transport Implementation) | +--------------------------------------------------------+ 
```
An upstream event is handled by the upstream handlers in the bottom-up direction as shown on the left side of the diagram. An upstream handler usually handles the inbound data generated by the I/O thread on the bottom of the diagram. The inbound data is often read from a remote peer via the actual input operation such as {@link InputStream#read(byte[])}. If an upstream event goes beyond the top upstream handler, it is discarded silently.
A downstream event is handled by the downstream handler in the top-down direction as shown on the right side of the diagram. A downstream handler usually generates or transforms the outbound traffic such as write requests. If a downstream event goes beyond the bottom downstream handler, it is handled by an I/O thread associated with the {@link Channel}. The I/O thread often performs the actual output operation such as {@link OutputStream#write(byte[])}.
For example, let us assume that we created the following pipeline:
```
 {@link ChannelPipeline} p = {@link Channels}.pipeline(); p.addLast("1", new UpstreamHandlerA()); p.addLast("2", new UpstreamHandlerB()); p.addLast("3", new DownstreamHandlerA()); p.addLast("4", new DownstreamHandlerB()); p.addLast("5", new UpstreamHandlerX()); 
```
In the example above, the class whose name starts with {@code Upstream} meansit is an upstream handler. The class whose name starts with {@code Downstream} means it is a downstream handler.
In the given example configuration, the handler evaluation order is 1, 2, 3, 4, 5 when an event goes upstream. When an event goes downstream, the order is 5, 4, 3, 2, 1. On top of this principle, {@link ChannelPipeline} skipsthe evaluation of certain handlers to shorten the stack depth:
- 3 and 4 don't implement {@link ChannelUpstreamHandler}, and therefore the actual evaluation order of an upstream event will be: 1, 2, and 5.
- 1, 2, and 5 don't implement {@link ChannelDownstreamHandler}, and therefore the actual evaluation order of a downstream event will be: 4 and 3.
- If 5 extended {@link SimpleChannelHandler} which implements both{@link ChannelUpstreamHandler} and {@link ChannelDownstreamHandler}, the evaluation order of an upstream and a downstream event could be 125 and 543 respectively.
Building a pipeline

A user is supposed to have one or more {@link ChannelHandler}s in a pipeline to receive I/O events (e.g. read) and to request I/O operations (e.g. write and close). For example, a typical server will have the following handlers in each channel's pipeline, but your mileage may vary depending on the complexity and characteristics of the protocol and business logic:
1. Protocol Decoder - translates binary data (e.g. {@link ChannelBuffer}) into a Java object.
2. Protocol Encoder - translates a Java object into binary data.
3. {@link ExecutionHandler} - applies a thread model.
4. Business Logic Handler - performs the actual business logic (e.g. database access).
and it could be represented as shown in the following example:
```
 {@link ChannelPipeline} pipeline = {@link Channels#pipeline() Channels.pipeline()}; pipeline.addLast("decoder", new MyProtocolDecoder()); pipeline.addLast("encoder", new MyProtocolEncoder()); pipeline.addLast("executor", new  {@link ExecutionHandler}(new  {@link OrderedMemoryAwareThreadPoolExecutor}(16, 1048576, 1048576))); pipeline.addLast("handler", new MyBusinessLogicHandler()); 
```
Thread safety

A {@link ChannelHandler} can be added or removed at any time because a{@link ChannelPipeline} is thread safe. For example, you can insert a{@link SslHandler} when sensitive information is about to be exchanged,and remove it after the exchange.
Pitfall

Due to the internal implementation detail of the current default {@link ChannelPipeline}, the following code does not work as expected if FirstHandler is the last handler in the pipeline:
```
 public class FirstHandler extends  {@link SimpleChannelUpstreamHandler} {{@code @Override}public void messageReceived( {@link ChannelHandlerContext} ctx, {@link MessageEvent} e) {// Remove this handler from the pipeline, ctx.getPipeline().remove(this); // And let SecondHandler handle the current event. ctx.getPipeline().addLast("2nd", new SecondHandler()); ctx.sendUpstream(e); } } 
```
To implement the expected behavior, you have to add SecondHandler before the removal or make sure there is at least one more handler between FirstHandler and SecondHandler. @author The Netty Project @author Trustin Lee @version $Rev: 2153 $, $Date: 2010-02-17 17:24:25 +0900 (Wed, 17 Feb 2010) $ @apiviz.landmark @apiviz.composedOf org.jboss.netty.channel.ChannelHandlerContext @apiviz.owns org.jboss.netty.channel.ChannelHandler @apiviz.uses org.jboss.netty.channel.ChannelSink - - sends events downstream

Examples of org.jboss.netty.channel.ChannelPipeline

        }
      }


      void onConnected()
      {
        ChannelPipeline channelPipeline = _channel.getPipeline();
        _readTimeOutHandler = (ExtendedReadTimeoutHandler)channelPipeline.get(GenericHttpClientPipelineFactory.READ_TIMEOUT_HANDLER_NAME);
        _readTimeOutHandler.start(channelPipeline.getContext(_readTimeOutHandler));


        TestHttpResponseProcessor testResponseProcessor =
            new TestHttpResponseProcessor(_msgList,_readTimeOutHandler);


            String uriString = "/test";

View Full Code Here

Examples of org.jboss.netty.channel.ChannelPipeline

    {
      @Override
      public ChannelPipeline getPipeline() throws Exception
      {
        // Create a default pipeline implementation.
        ChannelPipeline pipeline = new DefaultChannelPipeline();
        pipeline.addLast("decoder", new HttpRequestDecoder());
        pipeline.addLast("encoder", new HttpResponseEncoder());
        pipeline.addLast("deflater", new HttpContentCompressor());
        pipeline.addLast("handler", new HttpRequestHandler());
        return pipeline;
      }

View Full Code Here

Examples of org.jboss.netty.channel.ChannelPipeline


  void onTargetScnConnectSuccess()
  {
    _curState = State.TARGET_SCN_REQUEST_WRITE;


    ChannelPipeline channelPipeline = _channel.getPipeline();
    _readTimeOutHandler = (ExtendedReadTimeoutHandler)channelPipeline.get(GenericHttpClientPipelineFactory.READ_TIMEOUT_HANDLER_NAME);
    _readTimeOutHandler.start(channelPipeline.getContext(_readTimeOutHandler));


    BootstrapTargetScnHttpResponseProcessor targetResponseProcessor =
        new BootstrapTargetScnHttpResponseProcessor(this, _callback, _callbackStateReuse,
                                                    _checkpoint,
                                                    _remoteExceptionHandler, _readTimeOutHandler);

View Full Code Here

Examples of org.jboss.netty.channel.ChannelPipeline


  void onStartScnConnectSuccess()
  {
    _curState = State.START_SCN_REQUEST_WRITE;


    ChannelPipeline channelPipeline = _channel.getPipeline();
    _readTimeOutHandler = (ExtendedReadTimeoutHandler)channelPipeline.get(GenericHttpClientPipelineFactory.READ_TIMEOUT_HANDLER_NAME);
    _readTimeOutHandler.start(channelPipeline.getContext(_readTimeOutHandler));


    BootstrapStartScnHttpResponseProcessor sourcesResponseProcessor =
        new BootstrapStartScnHttpResponseProcessor(this, _callback, _callbackStateReuse,
                                                   _checkpoint,
                                                   _remoteExceptionHandler,

View Full Code Here

Examples of org.jboss.netty.channel.ChannelPipeline


  void onStreamConnectSuccess()
  {
    _curState = State.STREAM_REQUEST_WRITE;


    ChannelPipeline channelPipeline = _channel.getPipeline();
    _readTimeOutHandler = (ExtendedReadTimeoutHandler)channelPipeline.get(GenericHttpClientPipelineFactory.READ_TIMEOUT_HANDLER_NAME);
    _readTimeOutHandler.start(channelPipeline.getContext(_readTimeOutHandler));


    StreamHttpResponseProcessor streamResponseProcessor =
        new StreamHttpResponseProcessor(this, _callback, _callbackStateReuse, _readTimeOutHandler);


    StringBuilder uriString = new StringBuilder(10240);

View Full Code Here

Examples of org.jboss.netty.channel.ChannelPipeline

  @Override
  public ChannelPipeline getPipeline() throws Exception
  {


    // Create a default pipeline implementation.
    ChannelPipeline pipeline = pipeline();




    pipeline.addLast("auto group register ",
                     new ConnectionChannelRegistrationHandler(_serverContainer.getTcpChannelGroup()));


    if (Logger.getRootLogger().isTraceEnabled())
    {
      pipeline.addLast("netty server traffic",
                       new LoggingHandler("netty server traffic", InternalLogLevel.DEBUG, true));
    }


    pipeline.addLast("outbound statistics collector",
                     new OutboundContainerStatisticsCollectingHandler(
                         _serverContainer.getContainerStatsCollector()));


    ExtendedWriteTimeoutHandler writeTimeoutHandler =
        new ExtendedWriteTimeoutHandler("server container " + _serverContainer.getContainerStaticConfig().getId(),
                                        _serverContainer.getNetworkTimeoutTimer(),
                                        _serverContainer.getContainerStaticConfig().getWriteTimeoutMs(),
                                        true);


    ExtendedReadTimeoutHandler readTimeoutHandler =
        new ExtendedReadTimeoutHandler("server container " + _serverContainer.getContainerStaticConfig().getId(),
                                       _serverContainer.getNetworkTimeoutTimer(),
                                       _serverContainer.getContainerStaticConfig().getReadTimeoutMs(),
                                       true);
    pipeline.addLast("read timeout", readTimeoutHandler);


    //add a handler to deal with write timeouts
    pipeline.addLast("server container write timeout handler", writeTimeoutHandler);


    pipeline.addLast("decoder",
                     new SimpleBinaryDatabusRequestDecoder(_serverContainer.getCommandsRegistry(),
                                                           readTimeoutHandler,
                                                           _byteOrder));
    pipeline.addLast("encoder", new SimpleBinaryDatabusResponseEncoder());


    // Fix for DDSDBUS-1000
//    pipeline.addLast("executionHandler", _serverContainer.getNettyExecHandler());


    //Dummy handler that will be automatically replaced depending on the current command being
    //executed
    pipeline.addLast(SimpleBinaryDatabusRequestDecoder.REQUEST_EXEC_HANDLER_NAME,
                     new LoggingHandler("netty server traffic", InternalLogLevel.DEBUG, true));




    return pipeline;
  }

View Full Code Here

Examples of org.jboss.netty.channel.ChannelPipeline


  void onSourcesConnectSuccess()
  {
    _curState = State.SOURCES_REQUEST_WRITE;


    ChannelPipeline channelPipeline = _channel.getPipeline();
    _readTimeOutHandler =
        (ExtendedReadTimeoutHandler)channelPipeline.get(GenericHttpClientPipelineFactory.READ_TIMEOUT_HANDLER_NAME);
    _readTimeOutHandler.start(channelPipeline.getContext(_readTimeOutHandler));


    SourcesHttpResponseProcessor<DatabusRelayConnectionStateMessage> sourcesResponseProcessor =
        new SourcesHttpResponseProcessor<DatabusRelayConnectionStateMessage>(this, _callback,
            _callbackStateReuse, _readTimeOutHandler);

View Full Code Here

Examples of org.jboss.netty.channel.ChannelPipeline


  void onRegisterConnectSuccess()
  {
    _curState = State.REGISTER_REQUEST_WRITE;


    ChannelPipeline channelPipeline = _channel.getPipeline();
    _readTimeOutHandler =
        (ExtendedReadTimeoutHandler)channelPipeline.get(GenericHttpClientPipelineFactory.READ_TIMEOUT_HANDLER_NAME);
    _readTimeOutHandler.start(channelPipeline.getContext(_readTimeOutHandler));


    RegisterHttpResponseProcessor registerResponseProcessor =
        new RegisterHttpResponseProcessor(this, _callback, _callbackStateReuse, _readTimeOutHandler);


    final String url = createRegisterUrl();

View Full Code Here

Examples of org.jboss.netty.channel.ChannelPipeline

  {
    boolean debugEnabled = LOG.isDebugEnabled();


    _curState = State.STREAM_REQUEST_WRITE;


    ChannelPipeline channelPipeline = _channel.getPipeline();
    _readTimeOutHandler = (ExtendedReadTimeoutHandler)channelPipeline.get(GenericHttpClientPipelineFactory.READ_TIMEOUT_HANDLER_NAME);
    _readTimeOutHandler.start(channelPipeline.getContext(_readTimeOutHandler));


    StreamHttpResponseProcessor streamResponseProcessor =
        new StreamHttpResponseProcessor(this, _callback, _callbackStateReuse, _readTimeOutHandler);


    StringBuilder uriString = new StringBuilder(1024);

View Full Code Here

Examples of org.jboss.netty.channel.ChannelPipeline

  private final TimeoutPolicy _timeoutPolicy;


  public SimpleTestHttpClient(ChannelFactory channelFactory, TimeoutPolicy timeoutPolicy) throws Exception
  {
    _clientBootstrap = new ClientBootstrap(channelFactory);
    ChannelPipeline pipeline = createPipeline();
    _clientBootstrap.setPipeline(pipeline);
    _timeoutPolicy = timeoutPolicy;
  }

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.

Examples of ChannelPipeline

Creation of a pipeline

How an event flows in a pipeline

Building a pipeline

Thread safety

Pitfall

Creation of a pipeline

How an event flows in a pipeline

Building a pipeline

Thread safety

Creation of a pipeline

How an event flows in a pipeline

Building a pipeline

Thread safety

Pitfall

Examples of org.jboss.netty.channel.ChannelPipeline

Examples of org.jboss.netty.channel.ChannelPipeline

Examples of org.jboss.netty.channel.ChannelPipeline

Examples of org.jboss.netty.channel.ChannelPipeline

Examples of org.jboss.netty.channel.ChannelPipeline

Examples of org.jboss.netty.channel.ChannelPipeline

Examples of org.jboss.netty.channel.ChannelPipeline

Examples of org.jboss.netty.channel.ChannelPipeline

Examples of org.jboss.netty.channel.ChannelPipeline

Examples of org.jboss.netty.channel.ChannelPipeline