Hello Eugeny, > Looks like the application creates too many sockets (as I wrote in some of my > previous e-mails), so probably I don't need that multithreaded connection > manager - but simple connection manager, which closes sockets after they are > used and HttpMethod.releaseConnection is called, rather than keeps this > connection for later usage?
"The" (our) SimpleConnectionManager does not close sockets, so I suggest you look for a different name to avoid confusion. > If I write such connection manager, will that affect cookies and related > information for each host, which is being kept in the HttpClient somehow? No, cookies are kept in an HttpState object. Closing the socket connection after each request will only affect performance. hope that helps, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
