On 20/07/2004 0.13, Oleg Kalnichevski wrote:
Andrea,
The code you contributed has been committed to the 2.0 branch. Many
thanks for this contribution.
http://cvs.apache.org/viewcvs.cgi/jakarta-commons/httpclient/src/contrib/org/apache/commons/httpclient/contrib/pool/Attic/
I have applied some min
Andrea,
The code you contributed has been committed to the 2.0 branch. Many
thanks for this contribution.
http://cvs.apache.org/viewcvs.cgi/jakarta-commons/httpclient/src/contrib/org/apache/commons/httpclient/contrib/pool/Attic/
I have applied some minor corrections to the source code to make i
reflection to invoke 1.4
Socket#connect(SocketAddress, int) instead of using a controller thread
Oleg
-Original Message-
From: Andrea Fabris [mailto:[EMAIL PROTECTED]
Sent: Friday, May 07, 2004 13:17
To: Commons HttpClient Project
Subject: Re: MultiThreadedConnectionManager based on
.
Thanks,
Sam
-Original Message-
From: Andrea Fabris [mailto:[EMAIL PROTECTED]
Sent: Friday, May 07, 2004 7:17 AM
To: Commons HttpClient Project
Subject: Re: MultiThreadedConnectionManager based on commons pool
Thanks, Oleg.
I've just downloaded the 3.0 latest build, and i'll take
Thanks, Oleg.
I've just downloaded the 3.0 latest build, and i'll take a look at it
and how it solves the idle connection problem.
Right now, i need a way to use multithread with httpclient 2.0 (that is
stable), so i think i'll use the code i've sent (because, as you said,
the patch was applied
ThreadedConnectionManager based on commons pool
On 07/05/2004 10.38, Kalnichevski, Oleg wrote:
> Andrea,
>
> New HttpClient 3.0 API has not been properly documented yet (documentation and test
> case coverage will become a top priority right after the 3.0-alpha1 release). The
> i
On 07/05/2004 10.38, Kalnichevski, Oleg wrote:
Andrea,
New HttpClient 3.0 API has not been properly documented yet (documentation and test case coverage will become a top priority right after the 3.0-alpha1 release). The idle connection management with the multi-threaded connection manager does t
ECTED]
Sent: Friday, May 07, 2004 10:08
To: Commons HttpClient Project
Subject: Re: MultiThreadedConnectionManager based on commons pool
Thanks for your feedback!
Now i'll explain my thoughts about multithreaded manager.
The biggest problem tha manger has, is about the idle connection sta
Thanks for your feedback!
Now i'll explain my thoughts about multithreaded manager.
The biggest problem tha manger has, is about the idle connection status:
for a long time now, as stated by a lot of people, idle connections
where not handled well, because they remain in CLOSE_WAIT status when
code
contributions these days, especially if you would like to be mentioned
as the author of the code you contribute
Cheers,
Oleg
-Original Message-
From: Andrea Fabris [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 06, 2004 15:11
To: Commons HttpClient Project
Subject: MultiThreadedConnecti
HttpClient Project
Subject: MultiThreadedConnectionManager based on commons pool
Hello Everybody!
I'm Andrea from italy, and i'm very interested about the jakarta httpclient.
I tried it and i find it very easy to use, but i found (i wrote about it
some time ago) a bug in the multithredconnectionmanger.
It seems th
Hello Everybody!
I'm Andrea from italy, and i'm very interested about the jakarta httpclient.
I tried it and i find it very easy to use, but i found (i wrote about it
some time ago) a bug in the multithredconnectionmanger.
It seems that the opened connections are tested for closure only when
they
12 matches
Mail list logo
