Zulfi,
If you expect us to react on this report, you have to be a little more specific on how
exactly you measured the performance, exactly what kind of HTTP methods your tests
included, exactly what pre-release-candidate you are referring to, and what exactly
you mean by but it is still
Zulfi,
I ran the profiler on
HttpClient 2.0-alpha3 and
HttpClient 2.0 Branch latest CVS
I basically used Oleg's test case provided in the email thread you
mentioned (code included).
I turned off logging and stale connection checking. I ran the tests
against a local Tomcat on a Win2k Pro
Zulfi,
I ran the profiler on
HttpClient 2.0-alpha3 and
HttpClient 2.0 Branch latest CVS
I basically used Oleg's test case provided in the email thread you
mentioned (code included).
I turned off logging and stale connection checking. I ran the tests
against a local Tomcat on a Win2k Pro
I do not remember which earlier releases I used. I only remeber that it
did not have the rcX attached to it. I am not sure if it matters now. I
guess, the only thing we are concerned here is whether we can get
HttpClient performance better than JDK or not. If yes, then how do we
get it? I
(3) HttpClient handsomely beats HttpURLConnection when streaming out
entity enclosing requests (POST, PUT)
Hi Oleg,
I am a bit skeptical about your test#3 for POST. I am doing POST myself
but the performance of HttpClient is not better than
java.net.HttpURLConnection. I have posted another email
On Fri, 2004-08-20 at 21:23, Zulfi Umrani wrote:
(3) HttpClient handsomely beats HttpURLConnection when streaming out
entity enclosing requests (POST, PUT)
Hi Oleg,
I am a bit skeptical about your test#3 for POST. I am doing POST myself
but the performance of HttpClient is not better than
