Agreed. Relying on garbage collection is not really an option. There are only 2 real choices that I can see:
1) add a method on HttpMethod to explicitly close a connection. This would be the simplest solution, but I think it would also defeat the purpose of connection reuse.
2) add a system for cleaning up/closing unused connections, perhaps after some timeout period. This is the better solution I think. Sam, if i remember correctly, you proposed something like this as an addition to the MultithreadedHttpConnectionManager. I would still like to take this idea and make it a little more generic for use with all connections. Hopefully I will find some time to work on this soon.
Thanks,
Mike
OK .... I dont know how the entire HttpClient works .. but ...
doesn't the fact that the socket is in CLOSE_WAIT state ( because the HTTP server sent a TCP FIN ) means that the HttpClient cannot use the socket anymore ?
So I guess what I am asking is, does HttpClient "detect" that the socket to be reused cannot be reused anymore and then closes it and creates a new one ?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
