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 25372] - auto close idle connections
Date Fri, 09 Apr 2004 13:26:24 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=25372>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=25372

auto close idle connections





------- Additional Comments From olegk@apache.org  2004-04-09 13:26 -------
Mike, I understand that 'elegancy' is a matter of personal preference and is
subjective, so all I am trying is to see if there's another way to approach the
problem, which may not necessarily better or feasible at all.

Important question here if tcp/ip sockets stay open when java Socket instance
garbage-collected or not. I believe the socket should be closed when GCed.
That's why I feel I'd rather have the idle connection handler hold onto
connection managers than individual connections, thus allowing connections to be
GCed when no longer in use. All I am saying that my guts tell me that
IdleConnectionManager / HttpConnectionManager coupling seems (to me) slightly
more elegant than IdleConnectionManager / HttpConnection coupling.

Oleg

---------------------------------------------------------------------
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