hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26139] - Memory leak in MultiThreadedHttpClient caused by bad .equals()
Date Wed, 21 Jan 2004 21:26:03 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26139>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26139

Memory leak in MultiThreadedHttpClient caused by bad .equals()





------- Additional Comments From becke@u.washington.edu  2004-01-21 21:26 -------
Hi Roland,

> since socket factories can be provided from outside the HTTP Client itself,
> I'd rather not require them to be singletons. You couldn't enforce it anyway.
> #2 seems the best approach to me.

I agree that requiring them to be singletons is not the ultimate solution, since there is
no way to 
enforce that.  Unfortuantely, there is also no way to enforce that equals() works correctly
as well.  
My plan, yet to be implemented, is to do 2&3 for all of the various HttpClient classes,
and to add 
javadocs suggesting that all implementors do the same.  How does that sound?

Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org


Mime
View raw message