Netty in Action V5：深度探索Java网络编程框架

5星 · 超过95%的资源需积分: 11 160 浏览量更新于2024-07-23 收藏 3.33MB PDF 举报

"Netty_in_Action 最新的英文原版V5包含了完整的16章目录树，涵盖了Netty的基础、核心功能、示例应用以及高级主题，适合深入学习和理解Netty框架。" Netty是一个高性能、异步事件驱动的网络应用程序框架，用于快速开发可维护的高性能协议服务器和客户端。本书《Netty in Action》是学习Netty的重要参考资料，特别是这个V5版本，它详细介绍了Netty的各种特性和最佳实践。 Part 1: Getting Started 这部分介绍了Netty和Java NIO (Non-blocking I/O) API的关系，帮助读者建立基础。第一章讲解了Netty与Java标准I/O的区别，以及为什么选择Netty。第二章通过一个简单的Netty应用实例，让读者初步了解如何构建和运行Netty程序。第三章则深入到Netty的底层机制，从零开始构建网络应用。 Part 2: Core Functions/Parts 这部分详细阐述了Netty的核心组件和功能。第四章探讨了不同的传输层，如NioSocketChannel和NioServerSocketChannel。第五章讨论了Netty中的Buffer系统，这是处理网络数据传输的关键。第六章讲解了ChannelHandler，它是处理网络事件和数据的核心接口。第七章介绍编码解码机制，使开发者能够自定义数据转换规则。第八章列出了Netty提供的预置ChannelHandler和Codec，如HTTP、TCP/IP等。第九章则讲述了如何启动和配置Netty应用程序，包括Bootstrap类的使用。 Part 3: Netty by Example 这部分通过实例来展示Netty的使用。第十章讲解如何对代码进行单元测试，确保Netty应用的健壮性。第十一章涉及WebSockets的支持，展示了如何在Netty中实现WebSocket服务器和客户端。第十二章涵盖了SPDY协议，一种优化Web性能的协议。第十三章则讨论了通过UDP进行广播事件的实现。 Part 4: Advanced Topics 这部分深入到高级主题，帮助开发者解决更复杂的问题。第十四章指导如何实施自定义的编解码器，以满足特定需求。第十五章探讨了选择正确的线程模型，这对于性能优化至关重要。第十六章涉及在线程池中注销和重新注册EventLoop的场景。第十七章提供了实际案例研究，将理论知识与实际应用相结合。此外，书本还附有三个附录：A章介绍了如何参与Netty社区，获取帮助和贡献；B章推荐了其他相关的书籍；C章列举了与Netty相关的项目，供读者进一步探索。这本书对于Java开发者来说，是一份宝贵的资源，无论你是初学者还是经验丰富的开发者，都能从中获得关于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页未读，继续阅读

saulpaul

粉丝: 0
资源: 9

Netty in Action V5：深度探索Java网络编程框架

Netty_In_Action中文版.pdf

Netty_In_Action中文版（有目录）

Netty_In_Action中文版

java.lang.UnsatisfiedLinkError: no com_alibaba_nacos_shaded_io_grpc_netty_shaded_netty_transport_native_epoll_x86_64 in java.library.path

netty_transport_native_epoll_x86_64', trying other loading mechanism

rocketmq no netty_tcnative in java.library.path: [/usr/java/packages/lib, /lib, /usr/lib]

netty so_keepalive

netty HANDSHAKE_ISSUED

netty so_linger

java netty wss_netty实现websocket客户端（支持wss安全连接）

最新资源