Hi there,
I'm using HttpClient to make a lot of connexions to different servers.
I want to design my App as well as possible, and I've got some questions
about
HttpClient design principles.
I'm using the WorkManager API (JSR 233) in Glassfish to create works ( 1
work = 1 httpclient connection)
that are consumed by a thread pool. All that stuff with threads is done
by the server (I use
CommonWorkManager from Sun).
My question is :
As I can't create threads directly in the App server, I can't use the
MultiThreadedHttpConnectionManager...
Does somebody have an idea or an advice about the implementation of a
MultiThreadedHttpConnectionManager that would use the Work Manager, or
be used in the
Work Manager ?
[Warning: this question is really dumb->] Can I use as many HttpClient
instances as the number of
threads I have (about 5000) ?
Thanks for your advices, and for opening the discussion (that would make
my ideas clearer...)
Florent
--
Pingwy
27, rue des arènes
49100 Angers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
