Author: buildbot
Date: Mon Oct 8 15:47:26 2012
New Revision: 834466
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/asynchronous-client-http-transport.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified:
websites/production/cxf/content/docs/asynchronous-client-http-transport.html
==============================================================================
---
websites/production/cxf/content/docs/asynchronous-client-http-transport.html
(original)
+++
websites/production/cxf/content/docs/asynchronous-client-http-transport.html
Mon Oct 8 15:47:26 2012
@@ -127,7 +127,7 @@ Apache CXF -- Asynchronous Client HTTP T
<p>Also, the JAX-WS specification allows for generation of asynchronous
methods on generated proxies as well as using asynchronous methods on the
Dispatch objects. These methods can take an AsyncHandler object and return a
polling Future object so applications do not have to wait for the response.
With the HttpURLConnection based transport, CXF was forced to consume a
background thread for each outstanding request.</p>
-<p>CXF also has an HTTP client transport that is based on the <a shape="rect"
class="external-link"
href="http://hc.apache.org/httpcomponents-asyncclient-dev/index.html";>Apache
HTTP Components HttpAsyncClient</a> library. The HttpAsyncClient library uses
a non-blocking IO model. This allows many more requests to be outstanding
without consume extra background threads. It also allows greater control over
things like Keep-Alive handling which is very difficult or impossible with the
HttpURLConnection based transport. However, the non-blocking model does not
perform quite as well as the blocking model for pure synchronous
request/response transactions.</p>
+<p>CXF also has an HTTP client transport that is based on the <a shape="rect"
class="external-link"
href="http://hc.apache.org/httpcomponents-asyncclient-dev/index.html";>Apache
HTTP Components HttpAsyncClient</a> library. The HttpAsyncClient library uses
a non-blocking IO model. This allows many more requests to be outstanding
without consuming extra background threads. It also allows greater control
over things like Keep-Alive handling which is very difficult or impossible with
the HttpURLConnection based transport. However, the non-blocking model does
not perform quite as well as the blocking model for pure synchronous
request/response transactions.</p>
<p>By default, if the cxf-rt-transports-http-hc module is found on the
classpath, CXF will use the HttpAsyncClient based implementation for any Async
calls, but will continue to use the HttpURLConnection based transport for
synchronous calls. This allows a good balance of performance for the common
synchronous cases with scalability for the asynchronous cases. However, using
a contextual property of "use.async.http.conduit" and set to true/false, you
can control whether the async or blocking version is used. If "true", the
HttpAsyncClient will be used even for synchronous calls, if "false",
asynchronous calls will rely on the traditional method of using
HTTPURLConnection along with a work queue to mimic the asynchronocity.</p>
