[ANNOUNCEMENT] HttpComponents HttpCore 4.2-alpha2 Released

[Oleg Kalnichevski <ol...@apache.org>]

The Apache HttpComponents project is pleased to announce the release of
HttpComponents HttpCore 4.2-alpha2. This release comes with completely
redesigned and rewritten asynchronous HTTP protocol handlers. New
protocol handling API used in conjunction with connection pooling
components introduced in the previous ALPHA release is expected to make
development of asynchronous HTTP client agents and HTTP proxies easier
and less error prone.

Sample application shipped with the release include an example of an
HTTP file server capable of direct channel (zero copy) data transfer and
an example of a non-blocking, fully streaming reverse proxy.  

We are kindly asking the users of HttpCore to review and try out the new
protocol handlers and give us feedback while the 4.2 API is still not
final. If no major flaws are discovered the 4.2 API is expected to be
frozen with the next BETA release. 

Please note that new features included in this release are still
considered experimental and their API may change in the future ALPHA
releases. This release also marks the end of support for Java 1.3. As of
this release HttpCore requires Java 1.5 for all its components. Several
classes and methods deprecated between versions 4.0-beta1 and 4.0 GA
(more than two years ago) have been removed in this release.

Download -
<http://hc.apache.org/downloads.cgi>
Release notes -
<http://www.apache.org/dist/httpcomponents/httpcore/RELEASE_NOTES.txt>
HttpComponents site -
<http://hc.apache.org/>

About HttpComponents Core -
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: a blocking I/O model based
on the classic Java I/O and a 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.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org