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

Javadoc

Browse Source
This commit is contained in:
Trustin Lee 2009-06-17 05:09:45 +00:00
parent 262fd48e28
commit 1826b88622
3 changed files with 13 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/main/java/org/jboss/netty/bootstrap/ClientBootstrap.java
View File

@ -93,7 +93,8 @@ import org.jboss.netty.channel.SimpleChannelUpstreamHandler;
* <p>
* {@linkplain #setPipelineFactory(ChannelPipelineFactory) The second approach}
* is to specify a {@link ChannelPipelineFactory} by yourself and have full
* control over how a new pipeline is created. This approach is more complex:
* control over how a new pipeline is created. This approach is more complex
* than the first approach while it is much more flexible:
*
* <pre>
* ClientBootstrap b = ...;
@ -113,8 +114,6 @@ import org.jboss.netty.channel.SimpleChannelUpstreamHandler;
* {@link ClientBootstrap} instances as you want to apply different settings
* for different {@link Channel}s.
*
* TODO: Show how to shut down a service.
*
* @author The Netty Project (netty-dev@lists.jboss.org)
* @author Trustin Lee (tlee@redhat.com)
*

6
src/main/java/org/jboss/netty/bootstrap/ConnectionlessBootstrap.java
View File

@ -51,6 +51,7 @@ import org.jboss.netty.channel.SimpleChannelUpstreamHandler;
*
* <h3>Only for connectionless transports</h3>
*
* This bootstrap is for connectionless transports only such as UDP/IP.
* Use {@link ServerBootstrap} instead for connection oriented transports.
* Do not use this helper if you are using a connection oriented transport such
* as TCP/IP and local transport which accepts an incoming connection and lets
@ -100,7 +101,8 @@ import org.jboss.netty.channel.SimpleChannelUpstreamHandler;
* <p>
* {@linkplain #setPipelineFactory(ChannelPipelineFactory) The second approach}
* is to specify a {@link ChannelPipelineFactory} by yourself and have full
* control over how a new pipeline is created. This approach is more complex:
* control over how a new pipeline is created. This approach is more complex
* than the first approach while it is much more flexible:
*
* <pre>
* ConnectionlessBootstrap b = ...;
@ -120,8 +122,6 @@ import org.jboss.netty.channel.SimpleChannelUpstreamHandler;
* many {@link ConnectionlessBootstrap} instances as you want to apply
* different settings for different {@link Channel}s.
*
* TODO: Show how to shut down a service.
*
* @author The Netty Project (netty-dev@lists.jboss.org)
* @author Trustin Lee (tlee@redhat.com)
*

16
src/main/java/org/jboss/netty/bootstrap/ServerBootstrap.java
View File

@ -55,10 +55,11 @@ import org.jboss.netty.channel.SimpleChannelUpstreamHandler;
*
* <h3>Only for connection oriented transports</h3>
*
* Use {@link ConnectionlessBootstrap} instead for connectionless
* transports. Do not use this helper if you are using a connectionless
* transport such as UDP/IP which does not accept an incoming connection but
* receives messages by itself without creating a child channel.
* This bootstrap is for connection oriented transports only such as TCP/IP
* and local transport. Use {@link ConnectionlessBootstrap} instead for
* connectionless transports. Do not use this helper if you are using a
* connectionless transport such as UDP/IP which does not accept an incoming
* connection but receives messages by itself without creating a child channel.
*
* <h3>Parent channel and its children</h3>
*
@ -94,7 +95,7 @@ import org.jboss.netty.channel.SimpleChannelUpstreamHandler;
*
* <h3>Configuring a parent channel pipeline</h3>
*
* It is rare to configure the pipeline of a parent channel because what it is
* It is rare to customize the pipeline of a parent channel because what it is
* supposed to do is very typical. However, you might want to add a handler
* to deal with some special needs such as degrading the process
* <a href="http://en.wikipedia.org/wiki/User_identifier_(Unix)">UID</a> from
@ -132,7 +133,8 @@ import org.jboss.netty.channel.SimpleChannelUpstreamHandler;
* <p>
* {@linkplain #setPipelineFactory(ChannelPipelineFactory) The second approach}
* is to specify a {@link ChannelPipelineFactory} by yourself and have full
* control over how a new pipeline is created. This approach is more complex:
* control over how a new pipeline is created. This approach is more complex
* than the first approach while it is much more flexible:
*
* <pre>
* ServerBootstrap b = ...;
@ -152,8 +154,6 @@ import org.jboss.netty.channel.SimpleChannelUpstreamHandler;
* {@link ServerBootstrap} instances as you want to apply different settings
* for different {@link Channel}s.
*
* TODO: Show how to shut down a service.
*
* @author The Netty Project (netty-dev@lists.jboss.org)
* @author Trustin Lee (tlee@redhat.com)
*