深入理解Netty：实战篇

需积分: 10 37 浏览量更新于2024-07-23 收藏 3.3MB PDF 举报

"《Netty in Action》是Manning Publications在2013年发布的一本关于Netty框架的专业书籍，通过Manning Early Access Program (MEAP) 提供给读者。这本书详细介绍了Netty以及它与Java NIO API的关系，帮助读者从零开始学习Netty，涵盖核心功能、实例应用以及高级主题。" 《Netty in Action》分为四个部分： Part 1: Getting Started 这部分主要介绍Netty和Java NIO API的基础知识，包括Netty的基本概念以及如何构建第一个Netty应用程序。同时，它深入讲解了Netty从底层如何构建，让读者对Netty的工作原理有一个全面的理解。 Part 2: Core Functions/Parts 这一部分详细讲解了Netty的核心组件： - Transports: Netty的传输层，包括不同的I/O模型如NIO、OIO等。 - Buffers: Netty的高效内存管理机制，提供了比Java原生ByteBuffer更强大的功能。 - ChannelHandler: 处理网络事件的接口，用于定义网络通信的行为。 - Codec: 编解码器，Netty提供了一套强大的机制来处理数据的编码和解码。 - Provided Channel Handlers and Codecs: Netty提供的预定义处理器和编解码器，如HTTP、FTP等协议的实现。 Part 3: Netty by Example 这部分通过实例展示Netty的应用，如： - Unit-test your code: 教导读者如何为Netty代码编写单元测试，确保代码的健壮性。 - WebSockets: 实现WebSocket协议的示例，展示了Netty在现代Web通信中的应用。 - SPDY: SPDY协议的实现，一种优化网页加载速度的协议。 - Broadcasting events via UDP: 使用UDP进行事件广播，展示了Netty在多播和广播场景中的应用。 Part 4: Advanced Topics 这部分探讨了一些高级主题，帮助读者深入了解和优化Netty的使用： - Implement a custom codec: 自定义编解码器的实现，满足特定的协议需求。 - Choosing the right thread model: 选择合适的线程模型，优化Netty的并发性能。 - Deregister/re-register with EventLoop: 了解如何在事件循环中注销和重新注册通道，以应对动态调整的需求。 - Case studies: 提供实际案例分析，帮助读者解决实际开发中的问题。此外，书中有两个附录： - Appendix A: The community - how to get involved: 引导读者加入Netty社区，参与讨论和贡献。 - Appendix B: Related books: 推荐相关的书籍，扩展学习资源。 - Appendix C: Related projects: 列举了与Netty相关的其他项目，扩展了Netty生态系统。《Netty in Action》是一本全面且深入的Netty指南，适合希望掌握Netty并利用其构建高性能网络应用的开发者阅读。

ServerSocketChannel serverChannel = ServerSocketChannel.open();

ServerSocket ss = serverChannel.socket();

InetSocketAddress address = new InetSocketAddress(port);

ss.bind(address); #1

serverChannel.configureBlocking(false);

Selector selector = Selector.open();

serverChannel.register(selector, SelectionKey.OP_ACCEPT); #2

while (true) {

try {

selector.select(); #3

} catch (IOException ex) {

ex.printStackTrace();

// handle in a proper way

break;

}

Set readyKeys = selector.selectedKeys(); #4

Iterator iterator = readyKeys.iterator();

while (iterator.hasNext()) {

SelectionKey key = (SelectionKey) iterator.next();

iterator.remove(); #5

try {

if (key.isAcceptable()) {

ServerSocketChannel server = (ServerSocketChannel)

key.channel();

SocketChannel client = server.accept(); #6

System.out.println("Accepted connection from " +

client);

client.configureBlocking(false);

client.register(selector, SelectionKey.OP_WRITE 

SelectionKey.OP_READ, ByteBuffer.allocate(100)); #7

}

if (key.isReadable()) { #8

SocketChannel client = (SocketChannel) key.channel();

ByteBuffer output = (ByteBuffer) key.attachment();

client.read(output); #9

}

if (key.isWritable()) { #10

SocketChannel client = (SocketChannel) key.channel();

ByteBuffer output = (ByteBuffer) key.attachment();

output.flip();

client.write(output); #11

output.compact();

}

} catch (IOException ex) {

key.cancel();

try {

key.channel().close();

} catch (IOException cex) {

}

©Manning Publications Co. We welcome reader comments about anything in the manuscript - other than typos and

other simple mistakes. These will be cleaned up during production of the book by copyeditors and proofreaders.

http://www.manning-sandbox.com/forum.jspa?forumID=857

#1 Bind server to port

#2 Register the channel with the selector to be interested in new Client connections that get accepted

#3 Block until something is selected

#4 Get all SelectedKey instances

#5 Remove the SelectedKey from the iterator

#6 Accept the client connection

#7 Register connection to selector and set ByteBuffer

#8 Check for SelectedKey for read

#9 Read data to ByteBuffer

#10 Check for SelectedKey for write

#11 Write data from ByteBuffer to channel

This example is more complex than the previous version of EchoServer. This complexity is a

trade off; asynchronous code is typically more complicated than its synchronous counterpart.

Semantically, the original NIO and the new NIO.2 API are similar, but their implementations

are different. Well take a look the differences next, and well implement version 3 of

EchoServer.

1.3.4 EchoServer based on NIO.2

Unlike the original NIO implementation, NIO.2 allows you to issue IO operations and provide

what is called a completion handler (

CompletionHandler class). This completion handler

gets executed after the operation completes. Therefore, execution of the completion handler is

driven by the underlying system and the implementation is hidden from the developer. It also

guarantees that only one

CompletionHandler is executed for channel at the same time. This

approach helps to simplify the code because it removes the complexity that comes with

multithreaded execution.

The major difference between the original NIO and NIO.2 is that you dont have to check

whether an event accours on the Channel and then trigger some action. In NIO.2 you can just

trigger an IO operation and register a completion handler with it, this handler will then get

notified once the operation complates. This removes the need to create your own application

logic to check for completion, which itself results in unnecessary processing.

Now lets see how the same asynchronous EchoServer would be implemented with

NIO2,implementation as shown in the next listing.

Listing 1.7 EchoServer v3: NIO.2

public class PlainNio2EchoServer {

public void serve(int port) throws IOException {

System.out.println("Listening for connections on port " + port);

final AsynchronousServerSocketChannel serverChannel =

AsynchronousServerSocketChannel.open();

InetSocketAddress address = new InetSocketAddress(port);

serverChannel.bind(address); #1

final CountDownLatch latch = new CountDownLatch(1);

serverChannel.accept(null, new

CompletionHandler<AsynchronousSocketChannel, Object>() { #2

@Override

public void completed(final AsynchronousSocketChannel channel,

Object attachment) {

©Manning Publications Co. We welcome reader comments about anything in the manuscript - other than typos and

other simple mistakes. These will be cleaned up during production of the book by copyeditors and proofreaders.

http://www.manning-sandbox.com/forum.jspa?forumID=857

serverChannel.accept(null, this); #3

ByteBuffer buffer = ByteBuffer.allocate(100);

channel.read(buffer, buffer,

new EchoCompletionHandler(channel)); #4

}

@Override

public void failed(Throwable throwable, Object attachment) {

try {

serverChannel.close(); #5

} catch (IOException e) {

// ingnore on close

} finally {

latch.countDown();

}

});

try {

latch.await();

} catch (InterruptedException e) {

Thread.currentThread().interrupt();

}

private final class EchoCompletionHandler implements

CompletionHandler<Integer, ByteBuffer> {

private final AsynchronousSocketChannel channel;

EchoCompletionHandler(AsynchronousSocketChannel channel) {

this.channel = channel;

}

@Override

public void completed(Integer result, ByteBuffer buffer) {

buffer.flip();

channel.write(buffer, buffer, new CompletionHandler<Integer,

ByteBuffer>() { #6

@Override

public void completed(Integer result, ByteBuffer buffer) {

if (buffer.hasRemaining()) {

channel.write(buffer, buffer, this); #7

} else {

buffer.compact();

channel.read(buffer, buffer,

EchoCompletionHandler.this); #8

}

@Override

public void failed(Throwable exc, ByteBuffer attachment) {

try {

channel.close();

} catch (IOException e) {

// ingnore on close

}

});

}

©Manning Publications Co. We welcome reader comments about anything in the manuscript - other than typos and

other simple mistakes. These will be cleaned up during production of the book by copyeditors and proofreaders.

http://www.manning-sandbox.com/forum.jspa?forumID=857

@Override

public void failed(Throwable exc, ByteBuffer attachment) {

try {

channel.close();

} catch (IOException e) {

// ingnore on close

}

#1Bind Server to port

#2 Start to accept new Client connections. Once one is accepted the CompletionHandler will get called.

#3 Again accept new Client connections

#4 Trigger a read operation on the Channel, the given CompletionHandler will be notified once

something was read

#5 Close the socket on error

#6 Trigger a write operation on the Channel, the given CompletionHandler will be notified once

something was written

#7 Trigger again a write operation if something is left in the ByteBuffer

#8 Trigger a read operation on the Channel, the given CompletionHandler will be notified once

something was read

At first glance, it may look like more code than what you had when using the previous NIO

implementation. But notice that NIO.2 handles threading and the creation of the so-called

event loop for you. This approach simplifies the code needed to build a multithreaded NIO

application, even though it may not seem to be the case in this example. As the complexity of

the application increases, the gains become more evident because youll be producing cleaner

code.

In the next section, well look at some known problems that exist in the JDKs NIO

implementation.

1.4 NIO problems and how Netty comes to the rescue

In this section, well look at some problems and limitations of the Java NIO APIs and how Netty

addresses these issues. Having the NIO packages of the JDK is a great step in the right

direction, but users are limited in how they can use them. These issues are often the result of

design choices that were made in the past and arent easy to change now, others are defects.

1.4.1 Cross-platform and compatibility issues

NIO is low level and depends on how the operating system (OS) handles IO. So fulfilling the

requirement of having a unified API exposed in Java, which works and behaves the same on all

OSs, isnt trivial.

When using NIO you often find that your code works fine on Linux, for example, but has

problems on Windows. My general advice, even if youre not using NIO, but its more important

if you are, is to test on all the OSs you want to support or use. Even if all the tests pass on

your Linux workstation, be sure to verify it on the other OSs. If you dont verify, prepare to

have fun later.

other simple mistakes. These will be cleaned up during production of the book by copyeditors and proofreaders.

http://www.manning-sandbox.com/forum.jspa?forumID=857

Ideal as NIO.2 may seem, its only supported in Java 7, and if your application runs on Java

6, you may not be able to use it. Also, at the time of writing, there is no NIO.2 API for

datagram channels (for UDP applications), so its usage is limited to TCP applications only.

Netty addresses this problem by providing a unified API, which allows the same semantics

to work seamlessly on either Java 6 or 7. You dont have to worry about the underlying

version, and you benefit from a simple and consistent API.

1.4.2 Extending ByteBuffer ... or not

As you saw previously, ByteBuffer is used as data container. Unfortunately, the JDK doesnt

contain a

ByteBuffer implementation that allows wrapping an array of ByteBuffer

instances. This functionality is useful if you want to minimize memory copies. If you rethinking

Ill implement it myself, dont waste your time;

ByteBuffer has a private constructor, so it

isnt possible to extend it.

Netty provides its own

ByteBuffer implementation, which gets around this limitation and

goes further by providing several other means of constructing, using, and manipulating a

ByteBuffer all with a simpler API.

1.4.3 Scattering and gathering may leak

Many channel implementations support scattering and gathering. This feature allows writing to

or reading from many

ByteBuffer instances at the same time with better performance. Here

the kernel/OS handles how these are written/read, which often gives you the best performance

because the kernel/OS, being closer to the hardware, knows how to do it in the most efficient

way.

Scattering/gathering is often used if you want to split data in different

ByteBuffer

instances to handle each buffer separately. For example, you may want to have the header in

one

ByteBuffer and the body in another.

Figure 1.4 shows how a scattering read is performed. You pass an array of

ByteBuffer

instances to the

ScatteringByteChannel and the data gets scattered from the channel to

the buffers.

Figure 1.4 A scattering read from a channel

other simple mistakes. These will be cleaned up during production of the book by copyeditors and proofreaders.

http://www.manning-sandbox.com/forum.jspa?forumID=857

剩余264页未读，继续阅读

itd018

粉丝: 4
资源: 7

深入理解Netty：实战篇

netty in action.rar

netty in action中文版

netty in action 中文版

Netty in Action 2015实战指南

Netty in Action: 高性能Java网络编程英文版

Netty in Action 第五版：深度解析网络通信框架

Netty in Action - Norman Maurer, Marvin Allen Wolfthal

Netty in Action：第5版目录详解

Netty入门指南：理解网络编程和Netty框架基础

深入学习netty的书籍

最新资源