Hi, I am in need of handling burts requests and await the result of it, where the result is both capturing the http response code as well as minimal parsing of the body.
In the past, I've written a multi thread model which does this job, but have problems capturing the results properly, as I spawn threads, it sort of is done when these are all spawned. While I am only done when I have all the results. This should not block further requests (for burst requests) as well... Now that a new core is out (NIO) and well into beta, I think it is a good moment to make use of that. But what would be the best way? I am talking about high volume, high preformance here as this component runs from server side (EJB container), and I don't want to run into max-connections as such. I want to know exactly what is shared and what isn't, to avoid max-connections. Would the example mentioned: http://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk/module-client/src/examples/org/apache/http/examples/client/ClientMultiThreadedExecution.java the proper approach? Where I want to wrap a single burst in an Executor thread model, each with its own ConnectionManager. How would I effectively wait the results and then 'finish' the method? Before I go re-invent the wheel, I was hoping to receive some feedback from users who have experience in this use case. All suggestions and pointers are welcome! Thanks in advance, Mike Ahlers -- View this message in context: http://www.nabble.com/Bursts-of-concurrent-requests-questions-tp18887772p18887772.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]
