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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From [EMAIL PROTECTED] 2004-04-09 00:36 ------- Finally I found a little time to take a look at the patch. Somehow I can't help thinking that coupling IdleConnectionHandler with HttpConnection is not not ideal. What if one sets a ridiculously high idle timeout value? Connections would be piling up in the IdleConnectionHandler unnecessarily. I would rather see IdleConnectionHandler monitor connections of just one connection manager, and would rather have the IdleConnectionHandler stay alive as long as the connection manager itself stays alive. I understand your intention was to have only one dedicated thread watching over all active connections in order to conserve resources. I personally would rather prefer a little less resource efficient but slightly more elegant solution. Besides, do not we encourage people to have just one HttpClient instance with just one connection manager per application, do we? Or maybe I just desperately need some sleep. Let me know if my rumbling makes any sense at all. If it does not I'll try to give the problem another look tomorrow morning (I mean this morning) Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
