[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jmeter-user
Subject:    Re: Java HTTP implementation vs. Commons HttpClient
From:       sebb <sebbaz () gmail ! com>
Date:       2007-11-29 16:53:32
Message-ID: 25aac9fc0711290853g569cd47fv81f63e8d6120262c () mail ! gmail ! com
[Download RAW message or body]

On 29/11/2007, Modha Khammammettu <MKhammammettu@calcas.com> wrote:
> Hi
>
> Reading through the documentation I found this...
>
>
> http://jakarta.apache.org/jmeter/usermanual/component_reference.html#HTT
> P_Request
> There are two versions of the sampler - one uses the default Java HTTP
> implementation, the other uses Commons HttpClient.
> The default (Java) implementation has some limitations:
> *       There is no control over how connections are re-used. When a
> connection is released by JMeter, it may or may not be re-used by the
> same thread.
> *       The API is best suited to single-threaded usage - various
> settings (e.g. proxy) are defined via system properties, and therefore
> apply to all connections.
> *       There is a bug in the handling of HTTPS via a Proxy (the CONNECT
> is not handled correctly). See Java bugs 6226610 and 6208335.
>
>        Question: If Commons HttpClient has no issues then why not use
> that instead of default implementation.

To maintain backwards compatibility with existing test plans.
To provide choice.

>        Where do I specify that I want to use Commons HttpClient instead
> of default implementation.

Choose the sampler called:

HTTP Request HTTPClient


>        Please let me know.
>        Thanks
>
>
>

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

[prev in list] [next in list] [prev in thread] [next in thread]