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
Carl,
That's OK, the problem
I run into is that after running for not very long, I suddenly start
getting
everything timing out. It's hard to really pinpoint the timing, giving all
the
activity, and no thread identifiers in the log messages, but I think what
is
happening is that the
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
Dear Friends,
I'm using the HTTP Client in a pool of connection. I have created a
class that manage a list of URL. For example: i have a list of 100 URLs
of diferent hosts. I want to retrieve all this urls but i don't want
to do this in a sequencial mode. I want to put some connections in a
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 Nick,
I think I've confused myself and in turn this conversation. I think we
generally agree though. Here's the solutions that I would propose in
preferential order.
1. Add support for no-proxy URLs to HttpClient, so that you can set the
proxy host, port and a list of servers not to use the
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
