You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hc.apache.org by ol...@apache.org on 2009/02/05 21:27:14 UTC
svn commit: r741278 - /httpcomponents/project/src/site/apt/index.apt
Author: olegk
Date: Thu Feb 5 20:27:14 2009
New Revision: 741278
URL: http://svn.apache.org/viewvc?rev=741278&view=rev
Log:
Improved layout of the project front page
Modified:
httpcomponents/project/src/site/apt/index.apt
Modified: httpcomponents/project/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/httpcomponents/project/src/site/apt/index.apt?rev=741278&r1=741277&r2=741278&view=diff
==============================================================================
--- httpcomponents/project/src/site/apt/index.apt (original)
+++ httpcomponents/project/src/site/apt/index.apt Thu Feb 5 20:27:14 2009
@@ -46,53 +46,34 @@
HttpComponents Structure
- The HttpComponents project is in the process of developing low-level libraries for several
- aspects of the HTTP protocol. Users with advanced needs in server- or client-side HTTP
- communication may find this a useful toolset to build custom HTTP services.
+* HttpComponents Core
-* HttpCore
-
- The {{{httpcomponents-core/index.html}HttpCore}} components implement the most fundamental
- aspects of the HTTP protocol. They are nonetheless sufficient to develop basic client-side and
- server-side HTTP services with a minimal footprint and no external dependencies.
-
- HttpCore consists of several modules
-
-** HttpCore base module
-
- This module contains the HttpCore public API and the default implementation based on the Java
- classic (blocking) I/O model. It requires a Java 1.3 compatible runtime and has no dependency
- on any external libraries.
-
-** HttpCore NIO extensions
-
- HttpCore NIO extensions contain optional components that leverage the event driven, non-blocking
- I/O (NIO) model. HttpCore NIO extensions require a Java 5.0 compatible runtime and the HttpCore
- base module. HttpCore NIO extensions are intended for those usage scenarios where raw throughput
- is less important than the ability to handle thousands of simultaneous HTTP connections in a
- resource efficient manner.
-
-* HttpClient
-
- {{{httpcomponents-client/index.html}HttpClient}} provides components for client-side
- authentication, HTTP state management, connection management, and an HTTP/1.1 compliant
- HTTP agent implementation based on those components. It is intended as successor of and
- replacement for {{{http://hc.apache.org/httpclient-3.x/index.html}Jakarta
- Commons HttpClient 3.x}}
-
-** HttpClient base module
-
- The {{{httpcomponents-client/httpclient/index.html}HttpClient}} module is a full-featured,
- HTTP/1.1 compliant agent built on top of {{{httpcomponents-core/index.html}HttpCore}}.
-
-** HttpMime module
+ {{{httpcomponents-core/index.html}HttpCore}} 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.
+
+ 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.
- The {{{httpcomponents-client/httpmime/index.html}HttpMime}} module extends
- {{{http://james.apache.org/mime4j/index.html}mime4j}} library with some HTTP specific
- functionality and integrates it with the HttpComponents framework.
+ * HttpCore Tutorial ( {{{httpcomponents-core/tutorial/html}HTML}}
+ / {{{httpcomponents-core/tutorial/pdf/httpcore-tutorial.pdf}PDF}} )
+
+ * HttpCore {{{httpcomponents-core/examples.html}Samples}}
+
+* HttpComponents Client
+ {{{httpcomponents-client/index.html}HttpClient}} 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 intended as successor of and replacement for
+ {{{http://hc.apache.org/httpclient-3.x/index.html} Jakarta Commons HttpClient 3.x}}
-Commons HttpClient
+ * HttpClient {{{httpcomponents-client/examples.html}Samples}}
+
+* Commons HttpClient (legacy)
The Apache HttpComponents project is charged with developing and maintaining
{{{http://hc.apache.org/httpclient-3.x/index.html}Commons HttpClient}}.