Return-Path: 
 <httpclient-dev-return-11295-apmail-jakarta-httpclient-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-httpclient-dev-archive@www.apache.org
Received: (qmail 63510 invoked from network); 8 Jul 2005 09:20:41 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 8 Jul 2005 09:20:41 -0000
Received: (qmail 92990 invoked by uid 500); 8 Jul 2005 09:20:39 -0000
Delivered-To: apmail-jakarta-httpclient-dev-archive@jakarta.apache.org
Received: (qmail 92963 invoked by uid 500); 8 Jul 2005 09:20:39 -0000
Mailing-List: contact httpclient-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:httpclient-dev-unsubscribe@jakarta.apache.org>
List-Help: <mailto:httpclient-dev-help@jakarta.apache.org>
List-Post: <mailto:httpclient-dev@jakarta.apache.org>
List-Id: "HttpClient Project" <httpclient-dev.jakarta.apache.org>
Reply-To: "HttpClient Project" <httpclient-dev@jakarta.apache.org>
Delivered-To: mailing list httpclient-dev@jakarta.apache.org
Received: (qmail 92950 invoked by uid 99); 8 Jul 2005 09:20:38 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jul 2005 02:20:38 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [80.238.133.19] (HELO gimli.fangorn) (80.238.133.19)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jul 2005 02:20:37 -0700
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by gimli.fangorn (Postfix) with ESMTP id 1FEBA536E72
	for <httpclient-dev@jakarta.apache.org>;
 Fri,  8 Jul 2005 11:20:30 +0200 (CEST)
Message-ID: <42CE455D.6060305@odi.ch>
Date: Fri, 08 Jul 2005 11:20:29 +0200
From: =?ISO-8859-1?Q?Ortwin_Gl=FCck?= <odi@odi.ch>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050324)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: HttpClient Project <httpclient-dev@jakarta.apache.org>
Subject: Re: [Fwd: Re: [HttpClient] Patched archive]
References: <42CE4278.9070502@odi.ch>
In-Reply-To: <42CE4278.9070502@odi.ch>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


> Hi Ortwin,
> 
> I will let you know tomorrow if the patch you sent works in my setup.
> I have anyways an offtopic question regarding your statement taken from
> bugzilla
> <quote>
> Yes HttpClient uses java.net. No, HttpClient does not use SocketChannel
> (nio)
> nor Socket.connect with a timeout since those APIs appeared in JDK 1.4.
> HttpClient is however compatible with JDK 1.3.1.
> </quote>
> 
> In the light of this statement, how does the new abort feature handle
> limit situations of TCP state? AFAIK it is not possible to shut down
> imediately and in a clean way a socket before NIO. I have seen
> situations where a thread blocked in socket write operation (partial
> network failures, tcp buffer full) was imposible to be interrupted by
> other thread in any way (by calling socket close or other ways).
> So, what would happen if one thread executes a http method, and
> another tries to cancel it with an abort call? (hit escape in firefox
> kind of scenario).
> 
> Regards and thank you for your time,
> Horia

Horia,

HttpMethod.abort just calls HttpConnection.close. This in turn first
closes output and input streams and the closes the Socket. In my
experience this has never caused any problems. We have never received
notice from anybody that an abort was not immediate.

Ortwin Gl�ck

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