Hi Oleg, I wrote a layer on TOP of the package, that solves my needs. In short, I am using java 1.5 concurrency classes to deal with the problem. When all tasks are done, I have my aggregated result. So, no NIO effort here. If you like I can post code of it here?
Also, to make an observation, the HttpClient interface should implement ANOTHER interface imho, namely that of Callable, with that could nicely blend. This should not be much of an effort, and yes, it raises the package dependency to 1.5... Now, I am about to add yet another layer, which is the ability to handle bursts concurrently. And I have some specific questions about lifecycles and reusage. To keep it simple and abstract, should I instantiate a ConnectionManager at top level with 'enough' connections, or delegate it (so its get created for each burst, in here I know exactly the # of connections needed). Thanks in advance, Mike -- View this message in context: http://www.nabble.com/Bursts-of-concurrent-requests-questions-tp18887772p18959059.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]
