Apache HttpComponents简介

官方网站如上

Apache HttpComponents

The Apache HttpComponents™ project is responsible for creating and maintaining a toolset of low level Java components focused on HTTP and associated protocols.

This project functions under the Apache Software Foundation (http://www.apache.org), and is part of a larger community of developers and users.

Apache HttpComponents™工程项目负责管理建立和保护几组下层Java模块开发工具，那些模块主要就高度关注HTTP和有关协定。

那个工程项目是在Apache应用软件促进会下运转的(http://www.apache.org)，它是两个Villamblard的开发者和使用者街道社区的一小部分。

HttpComponents Overview

HttpComponents 简述

The Hyper-Text Transfer Protocol (HTTP) is perhaps the most significant protocol used on the Internet today. Web services, network-enabled appliances and the growth of network computing continue to expand the role of the HTTP protocol beyond user-driven web browsers, while increasing the number of applications that require HTTP support.

超文本传输协定(HTTP)可能是当今Internet上使用的最重要的协定。Web服务、支持网络的设备和网络计算的增长继续扩展了HTTP协定在使用者驱动的Web浏览器之外的作用，同时增加了需要HTTP支持的应用程序的数量。

Designed for extension while providing robust support for the base HTTP protocol, the HttpComponents may be of interest to anyone building HTTP-aware client and server applications such as web browsers, web spiders, HTTP proxies, web service transport libraries, or systems that leverage or extend the HTTP protocol for distributed communication.

为扩展设计,同时提供强劲的支持HTTP协定,HttpComponents可能会成为构建HTTP-aware客户机和服务器应用程序的人兴趣,那些应用程序包括web浏览器、web spider, HTTP代理,利用web服务传输库,或系统为分布式通信或扩展HTTP协定。

HttpComponents Core

is a set of low level HTTP transport components that can be used to build custom client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: blocking I/O model based on the classic Java I/O and non-blocking, event driven I/O model based on Java NIO.

HttpCore是几组低层HTTP传输模块，可用于构建自定义客户端和服务器端HTTP服务，占用最少。HttpCore支持两种I/O模型:基于经典Java I/O的阻塞I/O模型和基于Java NIO的非阻塞事件驱动I/O模型。

The blocking I/O model may be more appropriate for data intensive, low latency scenarios, whereas the non-blocking model may be more appropriate for high latency scenarios where raw data throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner.

阻塞I/O模型可能更适合于数据密集型、低延迟的场景，而非阻塞模型可能更适合于高延迟的场景，在那些场景中，原始数据吞吐量不如以资源有效的方式处理数千个并发HTTP连接的能力重要。

and

HttpComponents Client

is a HTTP/1.1 compliant HTTP agent implementation based on HttpCore. It also provides reusable components for client-side authentication, HTTP state management, and HTTP connection management. HttpComponents Client is a successor of and replacement for

. Users of Commons HttpClient are strongly encouraged to upgrade.

HttpClient是两个基于HttpCore的HTTP/1.1兼容的HTTP代理实现。它还为客户端身份验证、HTTP状态管理和HTTP连接管理提供了可重用模块。httpcomponent Client是Commons HttpClient 3.x的继承者和替代者。强烈建议使用Commons HttpClient的使用者进行升级。

and

HttpComponents AsyncClient

is a HTTP/1.1 compliant HTTP agent implementation based on HttpCore NIO and HttpClient components. It is a complementary module to Apache HttpClient intended for special cases where ability to handle a great number of concurrent connections is more important than performance in terms of a raw data throughput.

异步HttpClient是两个基于HttpCore NIO和HttpClient模块的HTTP/1.1兼容的HTTP代理实现。它是Apache HttpClient的两个补充模块，适用于处理大量并发连接的能力比处理原始数据吞吐量的性能更重要的特殊情况。

Commons HttpClient (legacy) (遗留)

Commons HttpClient 3.x codeline is at the end of life. All users of Commons HttpClient 3.x are strongly encouraged to upgrade to HttpClient 4.1.

Commons HttpClient 3.x代码线是生命的终结。所有的使用者的Commons HttpClient 3.x都强烈建议升级到HttpClient 4.1。

截止2020年2月13日 最新版本如下：