ServerBootstrap与Bootstrap类似，只不过这个是用于服务端的启动。下面看下具体的使用：
public class TimeServer {
public void bind(int port) throws Exception {
// 配置服务端的NIO线程组
EventLoopGroup bossGroup = new NioEventLoopGroup();
EventLoopGroup workerGroup = new NioEventLoopGroup();
try {
ServerBootstrap b = new ServerBootstrap();
b.group(bossGroup, workerGroup)
.channel(NioServerSocketChannel.class)
.option(ChannelOption.SO_BACKLOG, 1024)
.childHandler(new ChildChannelHandler());
// 绑定端口，同步等待成功
ChannelFuture f = b.bind(port).sync();
// 等待服务端监听端口关闭
f.channel().closeFuture().sync();
} finally {
// 优雅退出，释放线程池资源
bossGroup.shutdownGracefully();
workerGroup.shutdownGracefully();
}
}
private class ChildChannelHandler extends ChannelInitializer {
@Override
protected void initChannel(SocketChannel arg0) throws Exception {
arg0.pipeline().addLast(new TimeServerHandler());
}
}
/**
* @param args
* @throws Exception
*/
public static void main(String[] args) throws Exception {
int port = 8080;
if (args != null && args.length > 0) {
try {
port = Integer.valueOf(args[0]);
} catch (NumberFormatException e) {
// 采用默认值
}
}
new TimeServer().bind(port);
}
}
与上篇文章介绍的Bootstrap不同，这里传入了两个EventLoopGroup，其中bossGroup用于接收请求，workerGroup用于处理IO事件。Netty是Reactor模式的实现，有关Reactor模式请参考NIO技术概览。
这里传入的Channel类型是NioServerSocketChannel，与Bootstrap一样，在bind方法中会调用init方法，下面看下ServerBootstrap中init方法的实现：
@Override
void init(Channel channel) throws Exception {
final Map, Object> options = options0();
synchronized (options) {
setChannelOptions(channel, options, logger);
}
final Map, Object> attrs = attrs0();
synchronized (attrs) {
for (Entry, Object> e: attrs.entrySet()) {
@SuppressWarnings("unchecked")
AttributeKey 注意一下这段代码：
pipeline.addLast(new ServerBootstrapAcceptor(
ch, currentChildGroup, currentChildHandler, currentChildOptions, currentChildAttrs));
这段代码向pipeLine中添加了一个ServerBootstrapAcceptor对象，ServerBootstrapAcceptor对象也是一个Handler，看下ServerBootstrapAcceptor的定义：
private static class ServerBootstrapAcceptor extends ChannelInboundHandlerAdapter {
private final EventLoopGroup childGroup;
private final ChannelHandler childHandler;
private final Entry, Object>[] childOptions;
private final Entry, Object>[] childAttrs;
private final Runnable enableAutoReadTask;
ServerBootstrapAcceptor(
final Channel channel, EventLoopGroup childGroup, ChannelHandler childHandler,
Entry, Object>[] childOptions, Entry, Object>[] childAttrs) {
this.childGroup = childGroup;
this.childHandler = childHandler;
this.childOptions = childOptions;
this.childAttrs = childAttrs;
// Task which is scheduled to re-enable auto-read.
// It's important to create this Runnable before we try to submit it as otherwise the URLClassLoader may
// not be able to load the class because of the file limit it already reached.
//
// See https://github.com/netty/netty/issues/1328
enableAutoReadTask = new Runnable() {
@Override
public void run() {
channel.config().setAutoRead(true);
}
};
}
@Override
@SuppressWarnings("unchecked")
public void channelRead(ChannelHandlerContext ctx, Object msg) {
final Channel child = (Channel) msg;
child.pipeline().addLast(childHandler);
setChannelOptions(child, childOptions, logger);
for (Entry, Object> e: childAttrs) {
child.attr((AttributeKey ServerBootstrapAcceptor继承自ChannelInboundHandlerAdapter，用于处理Inbound事件，该类的主要功能就是在服务器端接收到请求之后，会返回一个NioSocketChannel对象作为参数msg传入channelRead方法中，用变量child来表示；然后把在TimeServer中传入的childHandler添加到child所对应的pipeLine中，然后把child注册到childGroup中，也就是TimeServer中定义的workerGroup。
接收请求的操作是在NioServerSocketChannel中的doReadMessages方法中实现的：
@Override
protected int doReadMessages(ListdoReadMessages方法在NioMessageUnsafe中的read方法中调用，然后会执行pipeline.fireChannelRead(readBuf.get(i));将SocketChannel对象传入，也就是channelRead方法中的msg参数。至此，一个请求已经接收完毕，通道之间的通信就会交给childGroup，也就是TimeServer中的workerGroup来处理。