olegk wrote:
>
> ThreadSafeClientConnManager and ThreadPoolExecutor serve completely
> different purposes and are complimentary in their functions. The former
> manages a pool of objects, whereas the latter manages threads of
> execution. One can use ThreadPoolExecutor to execute multiple requests
> that obtain connections from a connection pool managed by
> ThreadSafeClientConnManager.
>
Ah, I see. Then I'll ask the more direct question -- would it be possible/
reasonable to make the max pool size adjustable, similar to how
ThreadPoolExecutor manages its thread pool size?
olegk wrote:
>
>> It looks like there are a number of classes in that package to handle
>> general concurrency and I'm wondering why the concurrent* library wasn't
>> used.
>>
>
> There is a plenty of references to standard java.util.concurrent
> primitives in the TSCM classes, as far as I can tell.
>
Ok thanks for the clarification. To be honest I did not look that far into
the source code.
olegk wrote:
>
>> Is it true that HttpClient 4 already requires Java 1.5?
>>
>
> Yes, it is.
>
Ok. I'm guessing it's not something that could be handled by
retrotranslator to get a 1.4 compatible binary?
Thanks Oleg for taking your time to respond to my questions. I appreciate
it.
-Tom
--
View this message in context:
http://www.nabble.com/ThreadSafeClientConnManager-and-pool-size-tp21079444p21096080.html
Sent from the HttpClient-User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
