Now i'll explain my thoughts about multithreaded manager.
The biggest problem tha manger has, is about the idle connection status: for a long time now, as stated by a lot of people, idle connections where not handled well, because they remain in CLOSE_WAIT status when returned from the client to the pool until some client requests them back.
This is a waste of resources.
Now, after i noticed the bugzilla 25372 (is it closed, right now? I have some problems accessing CVS...), i downloaded the latest nigthly build and made a few test, but i discovered that the problem remains.
So i thought it would be easier to change the logic of the manager and to base it on a pool library that is known to work.
However, i see your point of view: it would be desiderable to limit the httpclient dependencies only to those libraries that are a must (eg: logging).
By the way, as stated by oleg, i'm goig to sign the Apache CLA and document better the code i attached in my prevoius mail, hoping that this code could be useful in the contrib branch.
Regards Andrea Fabris Errore Apertura DB
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
