gt; which avoids the overhead of establishing a new
> connection for each request.
> If you want to know how it works, feel free to look
> at
> the source code. It's open :-)
>
> cheers,
> Roland
>
>
>
>
>
> Cabbar Duzayak <[EMAIL PROTECTED]>
> 12
Hi,
I am trying to run the following code for
www.google.com:
Cookie cookie = initialState.getCookies()[0];
CookieSpec cs = CookiePolicy.getDefaultSpec();
Header h = cs.formatCookieHeader(cookie);
Cookie[] cookie2 = cs.parse(cookie.getDomain(), 80,
cookie.getPath(), cookie.getSecure(), h);
And,
kies
> themselves.
>
> The HttpClient is associated with a connection pool.
> If
> you require independently configured connection
> pools
> for each thread, you have to create multiple
> HttpClient
> objects. Otherwise, one HttpClient with
> MultiThreadedHCM
> is ok.
Hi,
I will be writing a gateway which will invoke URLs in
behalf of several threads and they will return the
content. Each thread needs to invoke different URLs
with different context (cookies, etc).
It looks like right way of doing this is to
instantiate the HttpClient once with
MultiThreadedHtt
