Cheers for that Roland,
I'm much clearer on it now. I'm still not sure of one
thing. If I have multiple threads trying to make http
connections - all to the same server - should I just
create a new URLConnection for each request (and let
URLConnection manage the resources) or is it would it
better to explicitly manage the pool using HttpClient?
Thanks alot.
--- Roland Weber <[EMAIL PROTECTED]> wrote:
> Hello Alex,
>
> ALEX HYDE wrote:
> > I've misunderstood what is being said here. If you
> are
> > only creating one client then surely you are not
> > pooling?
>
> Why not? A single HttpClient is perfectly capable of
> supporting
> multiple connections from different threads,
> provided that it
> is created on top of a thread safe connection
> manager such as
> the MultiThreadedConnectionManager.
>
> > Also, if you only have one connection and then
> that
> > gets broken do you have to manage this or is this
> > managed under the covers?
>
> The connection manager takes care of it. Just make
> sure you do
> release the connection, whether there is a problem
> or not. The
> call to method.releaseConnection() is best put into
> a finally{}
> block.
>
> > I guess I'm asking whether
> > an httpclient actually equates toa phyical
> > connection?
>
> No, it doesn't. An HttpClient equates to a single
> application,
> which can perform multiple requests over multiple
> connections,
> consecutively or in parallel from multiple threads.
>
> cheers,
> Roland
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
___________________________________________________________
NEW Yahoo! Cars - sell your car and browse thousands of new and used cars
online! http://uk.cars.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
