Changes since 4.0 Beta 3 * [HTTPASYNC-28] PoolEntry's expiry information is never updated. Contributed by Daniel Kulp Release 4.0 Beta 3 ------------------- The 4.0 BETA3 is a maintenance release that picks up the latest bug fixes in the core components. Changelog: * Upgraded HttpCore to version 4.2.2 * [HTTPASYNC-26] OSGi bundle import fix. Contributed by Daniel Kulp * [HTTPASYNC-25] AsyncSchemeRegistry instance set in the execution context takes precedence over the default one. Contributed by Daniel Kulp * Ported fix for HTTPCLIENT-1224 Contributed by Oleg Kalnichevski Release 4.0 Beta 2 ------------------- The 4.0 BETA2 release fixes a number of non-critical issues found since release 4.0-beta1 and introduces basic support for HTTP/1.1 response caching. Please note that caching for streaming HTTP exchanges is currently not supported. Users of previous releases of HttpAsyncClient are advised to upgrade. Changelog: * [HTTPASYNC-20] HTTP exchange can now be aborted with HttpUriRequest#abort(). Contributed by Oleg Kalnichevski * [HTTPASYNC-17] Caching HttpAsyncClient facade. Contributed by Clinton Nielsen * [HTTPASYNC-19] Fixed incorrect execution of message exchanges that span across multiple hosts (for instance, in case of a request redirect). Contributed by Oleg Kalnichevski * [HTTPASYNC-18] Fixed thread deadlock that could occur in the DefaultAsyncRequestDirector in case of a runtime exception. Contributed by Oleg Kalnichevski * [HTTPASYNC-15]: HttpAsyncClient hangs if connection leased from the pool gets immediately closed by the opposite endpoint. Contributed by Oleg Kalnichevski Release 4.0 Beta 1 ------------------- The 4.0 BETA1 release completes the application programming interface and the feature set of HttpAsyncClient and upgrades to the latest versions of core and client components (HttpCore 4.2-beta1 and HttpClient 4.2-beta1). As of this release HttpAsyncClient is expected to be API stable. Users of previous releases of HttpAsyncClient are advised to upgrade. Changelog: * [HTTPASYNC-11]: HttpAsyncClient fails to re-authenticate if connection is non-persistent. Contributed by Oleg Kalnichevski * [HTTPASYNC-5]: Allow customized LineParser for asynchronous connections. Contributed by Oleg Kalnichevski Release 4.0 Alpha 3 ------------------- The 4.0 ALPHA3 release largely completes the application programming interface and feature set of HttpAsyncClient. While the API may still change in the course of the ALPHA development phase, this is expected to be the last round of major API changes and the API is expected to be reasonably stable as of this release. We are kindly asking actual and prospective users of HttpAsyncClient to review its API, evaluate its functionality and give us feedback while the 4.0 API is still not final. If no major flaws are discovered the 4.0 API is expected to be frozen with the next BETA release. Changelog: * [HTTPASYNC-6]: Fixed NPE in the DefaultAsyncRequestDirector#responseCompleted method. Contributed by Oleg Kalnichevski Release 4.0 Alpha 2 ------------------- The second ALPHA release of HttpAsyncClient 4.0 comes with a number of important improvements and enhancements. As of this version HttpAsyncClient fully supports HTTP state management (cookies) and HTTP authentication (basic, digest, NTLM, spnego/kerberos). Connection management classes have been thoroughly reworked and improved. This version also improves support for zero copy file upload / download operations. The HttpAsyncClient 4.0 API is still considered experimental and is expected to change in the course of the ALPHA development phase. Please note that currently HttpAsyncClient DOES NOT support * Stateful HTTP connections Changelog: * [HTTPASYNC-3]: Fixed incorrect handling of expired I/O sessions by SessionPool. Contributed by Oleg Kalnichevski Release 4.0 Alpha 1 ------------------- HttpAsyncClient is a library for asynchronous client-side HTTP communication built on HttpCore NIO and HttpClient components. HttpAsyncClient is NOT meant to replace or supersede Apache HttpClient. It is a complementary library 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 or for those users who prefer event-driven APIs. The HttpAsyncClient 4.0 API is still very experimental and is expected to change in the course of the ALPHA development phase. Please note that currently HttpAsyncClient DOES NOT support * HTTP state management (cookies) * HTTP authentication * Stateful HTTP connections