So bottom line is:
1) To implement HTTP/1.1 persistent connections, use a single HttpClient instance that is reused to execute HttpMethods. Assuming of course, that the HTTP response also does not have "Connection: close", then we have HTTP persistent connections.
Yes, in particular, the MultithreadedHttpConnectionManager is probably what you want. It can be configured to restrict the total number of active connections. This will allow you to reuse connections, and while it does not remove all instances of CLOSE_WAIT sockets, it will limit them to a configurable number.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
