+1 to all of that. Well said Marc. > There are two usage models that I know of: > HttpClient and HttpMultiClient.
A third model, and the one I use almost exclusively, is to ignore HttpClient (and HttpMultiClient) altogether and just work with HttpMethod, HttpConnection and HttpState directly. > HttpClient is the original model and its design > is based on its initial usage inside Slide. When > the Commons project was created the HttpClient > portion was made public so it could be used by > more projects. It still has a lot of its > original flavor. > HttpMultiClient exists because I saw a need > that was not met by the existing HttpClient. It may make sense to eventually do away with HttpClient altogether, replacing it what is HttpMultiClient does now.
