Custom Connection Management

2008-06-12 Thread Quintin Beukes
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

Re: Higher Throughputs

2008-06-12 Thread Oleg Kalnichevski
Quintin Beukes wrote: Hey, I made some basic servlets to test throughputs for HttpClient, HttpCore and sun's sun.net.www.protocol.http.HttpURLConnection (or something along those lines, I don't have an API at hand now). I basically just put up an apache session listening on port 8580, and then

Re: Custom Connection Management

2008-06-12 Thread Sam Berlin
The internal connection manager, in a nutshell, is there to reduce the amount of times new connections have to be created prevent a server from being overloaded with too many connections. It exposes a lot of bells whistles (and HttpClient makes use of them) so that a single connection can be