My apologies for not getting feedback to you on this. I hope to be able to get
to it this weekend...
On Friday April 4 2003 10:45, Michael Becke wrote:
I'm not entirely sure about MultiThreadedConnectionManager. There
hasn't been any feedback since I posted my patch. I believe it is quite
Sergio,
I had posted a crude patch a few days ago that partially solves this problem.
It basically adds a wider connection pool that tracks free connections,
closing them when needed and blocking requests in order to maintain a maximum
number of open connections.
It is better, but still not
Sergio,
I had posted a crude patch a few days ago that partially solves this problem.
It basically adds a wider connection pool that tracks free connections,
closing them when needed and blocking requests in order to maintain a maximum
number of open connections.
It is better, but still not
First, let me say that finding HttpClient was this week's bacon-saver. The
other alternatives out there are, shall we say politely, a bit lacking.
I have, however, run into a couple of things. Apologies if these have been
covered before. I tried searching the archives, and found some close
On Thursday March 20 2003 17:43, Oleg Kalnichevski wrote:
Carl
First of all, many thanks for bringing these issues up
No problem. It's nice to see such positive and quick reponses!
I can provide example URLs, if this will help.
Please do so. It will help me testing
BTW, here is a quick patch to degrade the code to work with these types of
messages:
*** HttpParser.java~Tue Feb 25 10:22:00 2003
--- HttpParser.java Thu Mar 20 02:06:02 2003
***
*** 53,61
break;
}
buf.write(ch);
Hi Adrian,
OK, that sounds like a good approach. I'll play around with something and post
it back here if I get it to work for my use. Perhaps I can tweak
MultiThreadedHttpConnectionManager to take a parameter that caps the overall
pool size.
On Thursday March 20 2003 17:52, Adrian Sutton
