Return-Path: X-Original-To: apmail-announce-archive@www.apache.org Delivered-To: apmail-announce-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 391526092 for ; Sun, 31 Jul 2011 16:00:03 +0000 (UTC) Received: (qmail 67776 invoked by uid 500); 31 Jul 2011 15:59:51 -0000 Delivered-To: apmail-announce-archive@apache.org Received: (qmail 67196 invoked by uid 500); 31 Jul 2011 15:59:49 -0000 Mailing-List: contact announce-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list announce@apache.org Delivered-To: moderator for announce@apache.org Received: (qmail 58160 invoked by uid 99); 31 Jul 2011 08:01:19 -0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Subject: [ANNOUNCEMENT] HttpComponents HttpCore 4.1.3 (GA) Released From: Oleg Kalnichevski To: announce@apache.org, private@hc.apache.org, dev@hc.apache.org, httpclient-users@hc.apache.org Content-Type: text/plain; charset="UTF-8" Date: Sun, 31 Jul 2011 10:00:41 +0200 Message-ID: <1312099241.22381.7.camel@ubuntu> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit The Apache HttpComponents project is pleased to announce the release of HttpComponents HttpCore 4.1.3 (GA). This release fixes a critical regression introduced in version 4.1.2. Under special circumstances non-blocking SSL sessions may fail to terminate correctly if the opposite end shuts down connection without sending a 'close notify' message causing an infinite loop in the I/O dispatch thread. All users of HttpCore NIO are strongly advised to upgrade. Download - Release notes - HttpComponents site - 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: announce-unsubscribe@apache.org For additional commands, e-mail: announce-help@apache.org