Return-Path: Delivered-To: apmail-hc-commits-archive@www.apache.org Received: (qmail 97215 invoked from network); 2 Feb 2009 22:16:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Feb 2009 22:16:52 -0000 Received: (qmail 23142 invoked by uid 500); 2 Feb 2009 22:16:52 -0000 Delivered-To: apmail-hc-commits-archive@hc.apache.org Received: (qmail 23120 invoked by uid 500); 2 Feb 2009 22:16:52 -0000 Mailing-List: contact commits-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list commits@hc.apache.org Received: (qmail 23111 invoked by uid 99); 2 Feb 2009 22:16:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 14:16:52 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 22:16:50 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id D532A2388852; Mon, 2 Feb 2009 22:16:28 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r740126 - /httpcomponents/httpcore/trunk/src/docbkx/nio-ext.xml Date: Mon, 02 Feb 2009 22:16:28 -0000 To: commits@hc.apache.org From: sebb@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20090202221628.D532A2388852@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: sebb Date: Mon Feb 2 22:16:28 2009 New Revision: 740126 URL: http://svn.apache.org/viewvc?rev=740126&view=rev Log: Standardise on "thread-safe" rather than "thread safe" Modified: httpcomponents/httpcore/trunk/src/docbkx/nio-ext.xml Modified: httpcomponents/httpcore/trunk/src/docbkx/nio-ext.xml URL: http://svn.apache.org/viewvc/httpcomponents/httpcore/trunk/src/docbkx/nio-ext.xml?rev=740126&r1=740125&r2=740126&view=diff ============================================================================== --- httpcomponents/httpcore/trunk/src/docbkx/nio-ext.xml (original) +++ httpcomponents/httpcore/trunk/src/docbkx/nio-ext.xml Mon Feb 2 22:16:28 2009 @@ -342,8 +342,8 @@ IOSession iosession = sessionRequest.getSession(); ]]> - SessionRequest implementations are expected to be thread - safe. Session request can be aborted at any time by calling + SessionRequest implementations are expected to be + thread-safe. Session request can be aborted at any time by calling IOSession#cancel() from another thread of execution. Effectively non-blocking HTTP connections are wrappers around IOSession with HTTP specific functionality. Non-blocking HTTP connections are - stateful and not thread safe. Input / output operations on non-blocking HTTP connections + stateful and not thread-safe. Input / output operations on non-blocking HTTP connections should be restricted to the dispatch events triggered by the I/O event dispatch thread.

@@ -505,7 +505,7 @@ therefore they need to maintain their own execution context. Each non-blocking HTTP connection has an HttpContext instance associated with it, which can be used to maintain a processing state. The HttpContext - instance is thread safe and can be manipulated from multiple threads. + instance is thread-safe and can be manipulated from multiple threads. IOControl interface, which represents a subset of connection functionality for controlling interest in I/O even notifications. IOControl - instances are expected to be fully thread safe. Therefore + instances are expected to be fully thread-safe. Therefore IOControl can be used to request / suspend I/O event notifications from any thread. One must take special precautions when interacting with non-blocking connections. HttpRequest and HttpResponse - are not thread safe. It is generally advisable that all input / output + are not thread-safe. It is generally advisable that all input / output operations on a non-blocking connection are executed from the I/O event dispatch thread. @@ -1284,7 +1284,7 @@ }; ]]> - Request handlers must be implemented in a thread safe manner. Similarly to + Request handlers must be implemented in a thread-safe manner. Similarly to servlets, request handlers should not use instance variables unless access to those variables are synchronized. @@ -1345,7 +1345,7 @@ }; ]]> - Please note HttpResponse objects are not thread safe + Please note HttpResponse objects are not thread-safe and may not be modified concurrently. Non-blocking request handlers must ensure the HTTP response cannot be accessed by more than one thread at a time.