Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: "Commons HttpClient Project"
 <commons-httpclient-dev@jakarta.apache.org>
Message-ID: <3FB4E3E6.6080704@nose.ch>
Date: Fri, 14 Nov 2003 15:17:10 +0100
From: =?ISO-8859-1?Q?Ortwin_Gl=FCck?= <ortwin.glueck@nose.ch>
Organization: NOSE Applied Intelligence
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.5) Gecko/20031007
MIME-Version: 1.0
To: Commons HttpClient Project <commons-httpclient-dev@jakarta.apache.org>
Subject: Re: HttpMethodBase.releaseConnection() finished download
References: <3FB42E0D.1060207@upb.de>
 <5462899A-1652-11D8-99E6-00306557E112@u.washington.edu>
 <3FB4DCC7.7030908@upb.de>
In-Reply-To: <3FB4DCC7.7030908@upb.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Sven K�hler wrote:
>> Adding the ability to abort methods is planned for the 2.1 release, 
>> but I don't think anyone has begun work on it yet.  If you come up 
>> with a good solution that you are willing to submit we would be happy 
>> to make use of it.
> 
> 
> So what would you suggest how an abort should look like? For me, a 
> boolean paramter for the releaseConnection-method would be sufficient.
> (releaseConnection() would be a shortcut to releaseConnection(boolean) 
> than).
> 
> I need this now, so i would try to implement a patch.
> 

For semantic reasons I suggest an HttpMethod::abort() method. You will 
need to create a patch against CVS HEAD. Because for the 2.0 branch it 
is definitely too late for this feature.

Maybe we will even need a HttpClient::abortAll(), but then HttpClient 
would need to know all the methods it is currently executing. That is 
easy to implement however.

Odi


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