One of the worst mass bleaching events in history occurred in 1998 — which was also one of the hottest years on record, and like 2010, an El Nio year.
史上最严重的大规模珊瑚白化事件之一发生于1998年——该年也是有史以来最热的一年，与2010年一样，也是厄尔尼诺现象的一年。
Warmer sea temperatures caused by climate change and periodic El Nio events have caused large areas of coral to be wiped out in so-called "bleaching" events.
气候变化及周期性的厄尔尼诺现象引起的海水变暖，已经造成了大面积的珊瑚礁在所谓的“漂白”事件中消失殆尽。
The NIO endpoint works entirely different.
与上面相比，NIO端点的工作方式就完全不同了。
Follow these steps to create the NIO connector.
请按照以下步骤创建NIO连接器。
There are several challenges to using NIO. These are.
要想使用NIO，我们面临着如下几个挑战。
Overview of the Different End-Points - Servlet and nio.
概览不同的端点——Servlet和nio。
NIO channels can be asynchronously closed and interrupted.
可以异步地关闭和中断NIO通道。
It may encourage the further adoption of NIO on Web servers.
它可能鼓励进一步在Web服务器上采用NIO。
The new input/output (NIO) library was introduced with JDK 1.4.
新的输入/输出 (NIO)库是在JDK 1.4 中引入的。
The example NIO server was compared to Tomcat 5.0 under heavy load.
示例NIO服务器是在重负载下与Tomcat 5.0进行比较的。
NIO lets you return to the connection later and send additional data.
NIO允许随后再返回到这个连接并发送额外的数据。
The NIO framework can be used to build powerful server side application.
NIO框架可用来构建强大的服务器端应用。
In contrast, the NIO-based server's performance degraded in a linear fashion.
相反，基于NIO的服务器的性能则以线性方式下降。
Further performance optimizations (improved NIO-level file streaming support,...)
更进一步的的性能优化(改进的NIO级文件流支持，……)。
The server class holds the multiplexer loop, the heart of any NIO-based server.
server类拥有多路复用循环——任何基于NIO服务器的核心。
NIO servers are relieved of this and therefore can scale to larger Numbers of users.
NIO服务器完全不用担心这一点，因此它们可以扩展到大量用户。
More importantly, by using the NIO package it is possible to access a file as a CharSequence.
更重要的是，通过使用NIO包，将一个文件作为CharSequence 进行访问是可能的。
We have not yet started adding NIO.2 support to JRuby's core classes, but that will come soon.
JRuby的核心类目前还没有开始添加NIO.2支持，但很快就会开始。
This tutorial is intended for any programmer who wants to learn more about the JDK 1.4 NIO library.
本教程是为希望学习更多关于JDK 1.4NIO库的知识的所有程序员而写的。
Tomcat uses NIO (Non-blocking IO) to keep the connection alive without wasting the waiting threads.
Tomcat使用NIO（无阻塞IO）来保持连接活动，无需浪费等待中的线程。
You'll also learn about things you can only do with NIO, such as asynchronous I/O and direct buffers.
您还会了解只能通过NIO 来完成的工作，如异步I/O和直接缓冲区。
Before you begin with the application, you need to configure the NIO connector in Community Edition.
开始应用程序之前，您需要在Community Edition中配置NIO连接器。
Throughout the tutorial, we'll work with code samples that illustrate different aspects of the NIO library.
在本教程中，我们将使用展示nio库的不同方面的代码示例。
Before going any further, I must confess that I'm not sure I have fully grasped the logic behind the NIO.
在进一步讨论之前，我必须承认我不能确定我已经充分掌握了NIO背后的逻辑。
Many articles followed, explaining the basics of NIO and how to leverage the benefits of nonblocking channels.
下面的许多文章阐述了 NIO 的基本知识及如何利用非阻塞通道的好处。
The objective was to determine if NIO gives any considerable performance benefits and under what conditions.
目标是要确定NIO是否给出了大量的性能优势，以及是在什么条件下给出的。
TCP transport communication on JXTA is fully NIO enabled providing scalable message handling and throughput.
JXTA上的TCP传输通信完全是基于NIO的，因而能够提供可伸缩的消息处理和吞吐量。
As a result, many developers have given up on building a Servlet-based Web application server that implements NIO.
因此，许多开发人员放弃了创建基于Servlet并实现了NIO的Web应用程序服务器。
Filesystem operations (like symlinks, permissions, etc) are now almost all available through NIO.2's filesystem APIs.
文件系统操作(比如symlink和permission等等)现在几乎都可以通过NIO . 2的文件系统API来完成。
We will first delete the BIO connector that runs on port 8080, and then create a new NIO connector to run on the same port.
我们将首先删除在 8080端口上运行的BIO连接器，然后创建在此端口运行的新NIO 连接器。
应用推荐