On Wed, 2008-08-13 at 01:39 -0700, Mike Ahlers wrote: > 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? >
Hi Mike The best thing would be to open an issue in JIRA and attach the course code to it > 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... > HttpClient already depends on 1.5 anyways. That should not be a problem. Feel free to submit a patch. > 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). > It depends on whether you want to re-use connections from previous 'bursts' or not. Oleg > Thanks in advance, > Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
