Hello Sven
you don't specify the HttpState for a connection.
You specify it for each method execution:
HttpClient.executeMethod
(HostConfiguration, HttpMethod, HttpState)
If you have used the same client from different
threads without specifying different states, that
might be a problem.
regards,
Roland
Sven Köhler <[EMAIL PROTECTED]>
12.11.2003 14:27
Please respond to "Commons HttpClient Project"
To: Commons HttpClient Project
<[EMAIL PROTECTED]>
cc:
Subject: Re: Cookies, Chunked-Post & Threads
> 1. Cookie Container:
> Let every session use it's own HttpState object. That's where
> HTTP Client stores it's cookies. The only problem is that it's
> not serializable, so it won't work with persistent sessions.
That's OK, but how do i say which HttpState to use for which connection?
> 2. Thread Safety:
> HTTP Client is thread safe as long as you use a thread safe
> connection manager.
Perhaps that's a bug or just intended behaviour, but multiple
HttpClient-Object used from different threads using one
MultiThreadHttpConnectionManager doesn't seems to work properly.
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
