TomStrummer wrote:
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?
I think so, but I just do not see a point. Why not just setting a higher
connections per host number? TSCM does not pre-allocate connections, so
the pool will never grow, unless really needed.
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?
I have not used retrotranslator myself so I cannot really tell.
We held a poll on the minimal JRE level for HttpClient 4.0 about a year
ago, and if my memory does not fail me, not a single person voted in
favor of 1.4 compatibility:
http://www.nabble.com/-POLL--Minimal-JRE-for-HttpClient-4.0-to13874820.html#a13874820
If upgrading to Java 1.5 is not an option for you, consider using
HttpClient 3.1 or building a custom HTTP client based on HttpCore 4.0,
which is still Java 1.3 compatible.
Thanks Oleg for taking your time to respond to my questions. I appreciate
it.
You are welcome.
Cheers
Oleg
-Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
