On Wed, 2008-10-15 at 00:07 +0200, Oleg Kalnichevski wrote:

> It is a little more complex than that. You do not, as long as that
> instance is used for the entire lifespan of the application. One really
> ought to shut down the connection manager before it goes out of scope /
> becomes garbage. This is especially important for managed environments
> such as servlet containers where applications can be undeployed and
> redeployed.

Does "this instance" refer to the HttpClient, or to the
connectionmanager? I use one instance of DefaultHttpClient during the
lifetime of my application. Does this client create new connection
managers that I have to shutdown, or does it use one connectionmanager?

Christine

-- 
dagdag is just a two character rotation of byebye
www.christine.nl


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to