.05.2004 12:26
> Please respond to "Commons HttpClient Project"
>
> To: Commons HttpClient Project
> <[EMAIL PROTECTED]>
> cc:
> Subject:Re: HttpClient
> initialization, when/where?
>
>
> Can you please elabo
zayak <[EMAIL PROTECTED]>
12.05.2004 12:26
Please respond to "Commons HttpClient Project"
To: Commons HttpClient Project
<[EMAIL PROTECTED]>
cc:
Subject:Re: HttpClient initialization, when/where?
Can you please elaborate a bit h
Can you please elaborate a bit how this connection
pool and multithreaded HCM work? Cause, given that
httpclient will be executed within my thread, why do
we need a multithreaded HCM? Also, connection pool is
used for sharing connections between threads? How
exactly does it work, what does it impro
Duzayak (I hope I got your name right),
You can create an instance of the HttpState class per thread and pass the respective
HttpState object along with the HTTP method to be executed:
// shared by all the worker threads
HttpConnectionManager connman = new MultiThreadedHttpConnectionManager();
Hello,
you need one HttpState for each thread, since the cookies
are stored there. Creating a new state for each request will
not work, unless the threads manage the cookies themselves.
The HttpClient is associated with a connection pool. If
you require independently configured connection pools
f
