Hey, HttpClient is great. Funny enough HttpClient is faster than HttpCore. I couldn't compare it to NIO, because the NIO examples didn't want to work with me. It's like the connections only paused and didn't continue, eventually just timeing out. I didn't research it further since the throughputs on HttpClient was sufficient.
Eitherhow, let me get to the point. I am using HttpClient to fetch some of my resources of backend servers. So far it's been perfect for this, but I want to do some optimizations. I have made two separate connection managers and then have maps to select which I want to use, based on the resource I want to fetch. I was hoping to combine this all into a single connection manager that selects the resource based on the URL and previous history (which it builds up over time). These smart selections are complex, so I'm not going to describe them here. They are irrelevant to my question anyhow. My question is basically how I would approach this. I assume I have to extend connection manager and supply it to the constructor of DefaultHttpClient. But what now? What do I have to do to manage persistent connections? How do I store/retrieve information on connections? How do I return such connections? How does all this work? If anyone could guide me, or point me in the right direction (docs, examples, etc) it would all be greatly appreciated. -- Quintin Beukes --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
