hc-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ol...@apache.org
Subject svn commit: r1195177 - in /httpcomponents/httpclient/trunk: fluent-hc/src/site/apt/index.apt src/site/site.xml
Date Sun, 30 Oct 2011 15:31:47 GMT
Author: olegk
Date: Sun Oct 30 15:31:46 2011
New Revision: 1195177

URL: http://svn.apache.org/viewvc?rev=1195177&view=rev
Log:
Fluent HC site updates

Modified:
    httpcomponents/httpclient/trunk/fluent-hc/src/site/apt/index.apt
    httpcomponents/httpclient/trunk/src/site/site.xml

Modified: httpcomponents/httpclient/trunk/fluent-hc/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/httpcomponents/httpclient/trunk/fluent-hc/src/site/apt/index.apt?rev=1195177&r1=1195176&r2=1195177&view=diff
==============================================================================
--- httpcomponents/httpclient/trunk/fluent-hc/src/site/apt/index.apt (original)
+++ httpcomponents/httpclient/trunk/fluent-hc/src/site/apt/index.apt Sun Oct 30 15:31:46 2011
@@ -31,13 +31,12 @@
 Fluent HC
 
 		This module provides an easy to use facade API for HttpClient based on the concept of
-		a fluent interface. Fluent HC exposes only the most fundamental functions of HttpClient
-		and is likely to be suitable mostly for simple use cases that do not require the full
-		flexibility of HttpClient. For instance, Fluent HC API relieves the users from having
-		to deal with resource deallocation and connection management. In most cases, though,
-		this comes at a price of having to buffer content of response messages in memory. However,
-		users can still use custom response handlers to process response streams of arbitrary
-		length.
+		a fluent interface. Fluent facade API exposes only the most fundamental functions of
+        HttpClient and is indended for simple use cases that do not require the full flexibility

+        of HttpClient. For instance, fluent facade API relieves the users from having to
deal with 
+        connection management and resource deallocation. In most cases, though, this comes
at
+        a price of having to buffer content of response messages in memory. However, users
can 
+        still use custom response handlers to process response streams of arbitrary length.
 
 ----------------------------------
 String result1 = Request.Get("http://somehost/")
@@ -92,8 +91,6 @@ Document result3 = Request.Get("http://s
 });
 ----------------------------------
 
-    Project reports:
-
     {{{./apidocs/index.html}Javadocs}}
 
     {{{./xref/index.html}Project sources}}
@@ -101,3 +98,4 @@ Document result3 = Request.Get("http://s
     {{{./dependencies.html}Dependencies}}
 
     {{{./issue-tracking.html}Issue Tracking}}
+

Modified: httpcomponents/httpclient/trunk/src/site/site.xml
URL: http://svn.apache.org/viewvc/httpcomponents/httpclient/trunk/src/site/site.xml?rev=1195177&r1=1195176&r2=1195177&view=diff
==============================================================================
--- httpcomponents/httpclient/trunk/src/site/site.xml (original)
+++ httpcomponents/httpclient/trunk/src/site/site.xml Sun Oct 30 15:31:46 2011
@@ -43,6 +43,7 @@
       <item name="HttpClient" href="httpclient/index.html"/>
       <item name="HttpMime" href="httpmime/index.html"/>
       <item name="HttpClient Cache" href="httpclient-cache/index.html"/>
+      <item name="Fluent HC" href="fluent-hc/index.html"/>
     </menu>
     <!-- Reports don't really apply at this level; in particular the dependecy report
is misleading -->
     <!-- menu ref="reports"/-->



Mime
View raw message