andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated documentation

Browse Source
This commit is contained in:
Trustin Lee 2010-02-17 08:24:25 +00:00
parent 8841f6897f
commit 49f548bc5d
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
src/main/java/org/jboss/netty/channel/ChannelPipeline.java
View File

@ -35,10 +35,11 @@ import org.jboss.netty.handler.ssl.SslHandler;
* and how the {@link ChannelHandler}s in the pipeline interact with each other. * and how the {@link ChannelHandler}s in the pipeline interact with each other.
* *
* <h3>Creation of a pipeline</h3> * <h3>Creation of a pipeline</h3>
* <p> *
* For each new channel, a new pipeline must be created. If a new pipeline is * For each new channel, a new pipeline must be created and attached to the
* attached to a channel, the coupling is permanent; the channel cannot attach * channel. Once attached, the coupling between the channel and the pipeline
* another pipeline to it nor detach the current pipeline from it. * is permanent; the channel cannot attach another pipeline to it nor detach
* the current pipeline from it.
* <p> * <p>
* The recommended way to create a new pipeline is to use the helper methods in * The recommended way to create a new pipeline is to use the helper methods in
* {@link Channels} rather than calling an individual implementation's * {@link Channels} rather than calling an individual implementation's
@ -49,7 +50,7 @@ import org.jboss.netty.handler.ssl.SslHandler;
* </pre> * </pre>
* *
* <h3>How an event flows in a pipeline</h3> * <h3>How an event flows in a pipeline</h3>
* <p> *
* The following diagram describes how {@link ChannelEvent}s are processed by * The following diagram describes how {@link ChannelEvent}s are processed by
* {@link ChannelHandler}s in a {@link ChannelPipeline} typically. * {@link ChannelHandler}s in a {@link ChannelPipeline} typically.
* A {@link ChannelEvent} can be handled by either a {@link ChannelUpstreamHandler} * A {@link ChannelEvent} can be handled by either a {@link ChannelUpstreamHandler}