hc-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ol...@apache.org
Subject svn commit: r741277 - in /httpcomponents/httpcore/trunk: doap_HttpComponents_Core.rdf src/site/apt/index.apt src/site/site.xml
Date Thu, 05 Feb 2009 20:26:48 GMT
Author: olegk
Date: Thu Feb  5 20:26:48 2009
New Revision: 741277

URL: http://svn.apache.org/viewvc?rev=741277&view=rev
Log:
Improved layout of the HttpCore front page; project description update

Modified:
    httpcomponents/httpcore/trunk/doap_HttpComponents_Core.rdf
    httpcomponents/httpcore/trunk/src/site/apt/index.apt
    httpcomponents/httpcore/trunk/src/site/site.xml

Modified: httpcomponents/httpcore/trunk/doap_HttpComponents_Core.rdf
URL: http://svn.apache.org/viewvc/httpcomponents/httpcore/trunk/doap_HttpComponents_Core.rdf?rev=741277&r1=741276&r2=741277&view=diff
==============================================================================
--- httpcomponents/httpcore/trunk/doap_HttpComponents_Core.rdf (original)
+++ httpcomponents/httpcore/trunk/doap_HttpComponents_Core.rdf Thu Feb  5 20:26:48 2009
@@ -46,11 +46,13 @@
 including support for NIO.
     </shortdesc>
     <description>
-HttpCore (main) is a library for HTTP communication that can be used
-on either client or server side. A second library, HttpCore-NIO, adds
-support for Java NIO. HttpCore has no dependencies beyond the JVM, but
-also no built-in support for advanced features such as cookie management
-or authentication. It defines a framework for plugging in these features.
+    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.
     </description>
     <bug-database rdf:resource="http://issues.apache.org/jira/browse/HTTPCORE" />
     <mailing-list rdf:resource="http://httpcomponents.apache.org/mail-lists.html" />
@@ -78,6 +80,11 @@
         <created>2008-06-22</created>
         <revision>4.0-beta2</revision>
       </Version>
+      <Version>
+        <name>HttpComponents Core 4.0-beta3</name>
+        <created>2008-10-19</created>
+        <revision>4.0-beta3</revision>
+      </Version>
     </release>
 
     <repository>

Modified: httpcomponents/httpcore/trunk/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/httpcomponents/httpcore/trunk/src/site/apt/index.apt?rev=741277&r1=741276&r2=741277&view=diff
==============================================================================
--- httpcomponents/httpcore/trunk/src/site/apt/index.apt (original)
+++ httpcomponents/httpcore/trunk/src/site/apt/index.apt Thu Feb  5 20:26:48 2009
@@ -34,27 +34,26 @@
 
 HttpCore Overview
 
-    HttpCore components implement the most fundamental aspects of the HTTP protocol that

-    are nonetheless sufficient to develop full-featured client-side and server-side HTTP

-    services with a minimal footprint.
-
-Modules
-
-    HttpCore has a modular structure with a base module and a number of specialized 
-    extensions.
-
-* HttpCore base module
-
-    The {{{httpcore/index.html}Base}} module contains the HttpCore public API and the 
-    default implementation based on the classic (blocking) Java I/O model. It 
-    requires a Java 1.3 compatible runtime and has no dependency on any external libraries.
+    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.
 
-* HttpCore NIO extensions
+    * {{{httpcore/index.html}HttpCore}}
 
-    HttpCore {{{httpcore-nio/index.html}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/index.html}HttpCore NIO}}
+    
+Documentation
 
+    * HttpCore Tutorial ( {{{tutorial/html}HTML}} / {{{tutorial/pdf/httpcore-tutorial.pdf}PDF}}
)
+    
+    * Some examples of HttpCore components in action can be found {{{examples.html}here}}
+    
 Standards Compliance
 
     HttpCore components strive to conform to the following specifications endorsed by the
Internet 
@@ -64,6 +63,3 @@
 
     * {{{http://www.ietf.org/rfc/rfc2616.txt}RFC 2116}} - Hypertext Transfer Protocol --
HTTP/1.1
     
-Examples
-
-    Some examples of HttpCore components in action can be found {{{examples.html}here}}

Modified: httpcomponents/httpcore/trunk/src/site/site.xml
URL: http://svn.apache.org/viewvc/httpcomponents/httpcore/trunk/src/site/site.xml?rev=741277&r1=741276&r2=741277&view=diff
==============================================================================
--- httpcomponents/httpcore/trunk/src/site/site.xml (original)
+++ httpcomponents/httpcore/trunk/src/site/site.xml Thu Feb  5 20:26:48 2009
@@ -49,6 +49,7 @@
     <menu name="HttpCore Overview">
       <item name="Description" href="index.html"/>
       <item name="Download" href="download.html"/>
+      <item name="Tutorial" href="tutorial/html/index.html"/>
       <item name="Examples" href="examples.html"/>
     </menu>
     <menu name="Modules">



Mime
View raw message