Return-Path: Delivered-To: apmail-hc-dev-archive@www.apache.org Received: (qmail 99202 invoked from network); 15 Jan 2009 01:22:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Jan 2009 01:22:51 -0000 Received: (qmail 72610 invoked by uid 500); 15 Jan 2009 01:22:51 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 72584 invoked by uid 500); 15 Jan 2009 01:22:51 -0000 Mailing-List: contact dev-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 dev@hc.apache.org Received: (qmail 72573 invoked by uid 99); 15 Jan 2009 01:22:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jan 2009 17:22:51 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of chasw3@gmail.com designates 209.85.218.20 as permitted sender) Received: from [209.85.218.20] (HELO mail-bw0-f20.google.com) (209.85.218.20) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jan 2009 01:22:43 +0000 Received: by bwz13 with SMTP id 13so1578523bwz.22 for ; Wed, 14 Jan 2009 17:22:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=xJCj+a3c/FKwzsahMRIUgiuvFvUcloMpvrfoljutuu8=; b=h+Uko3gQsLwUPvx0kwSDFXjfbCntlUhw4KTH3Lc/f8KZjQPQ5qrjy3w8DJNXphyGTo t4Xivnx+rRABeNW2Oua32GUFNN7jK+pcPWdPXwh5M0OhJedeJFJXwmtnio0Z04YKQPRR +2LMLFra1PNc6veADVK7+WA/vbUqw4AA6SWD4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=skWuJqCuzPlOj/uk6X0vHf9LgndpfZUGwz8My5GFGclB3t978aILo+1k0IR3FiUh9Y rNBxb9JBySw171P2TNYuqcMP3t4AC6dChslbum56Wcm4LmTBZjSUvU+BZnPyK+ATEJPk t591dghqROGl7yH6nbcqNhVBfZ19rDt41bivo= Received: by 10.103.182.3 with SMTP id j3mr380826mup.107.1231982542420; Wed, 14 Jan 2009 17:22:22 -0800 (PST) Received: by 10.103.238.13 with HTTP; Wed, 14 Jan 2009 17:22:22 -0800 (PST) Message-ID: <6ccb72640901141722v21e3e807m5c794089e2e65655@mail.gmail.com> Date: Wed, 14 Jan 2009 17:22:22 -0800 From: "Chas Williams" To: "HttpComponents Project" Subject: HttpCore NIO extensions -- SessionRequestCallback vs. EventListener? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_941_29580151.1231982542412" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_941_29580151.1231982542412 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello, I'm running a high throughput nio http client (essentially a small webcrawler) through the apache HttpCore NIO extensions -- my code is based largely off the sample client at http://svn.apache.org/repos/asf/httpcomponents/httpcore/trunk/module-nio/src/examples/org/apache/http/examples/nio/NHttpClient.java . I'm modeling my work flow using 'work object' attachments that are passed around by threads, or sometimes placed in queues (or requested from the web by the httpcore nio extensions). I need to very precisely react to each different kind of request failure a single time -- but I'm having a difficult time understanding the difference between SessionRequestCallback and EventListener. I've looked through the JavaDoc, but can't find guarantees anywhere of which callback methods are used, when, and why. For example, in my EventListener object, I've seen calls for connectionTimeout followed by calls to fatalIOException. Is this intended behavior? Is there somewhere I can look for a more detailed description of these classes? Thanks much, Chas Williams chasw3@gmail.com ------=_Part_941_29580151.1231982542412--