sanghwa-min commented on PR #714: URL: https://github.com/apache/httpcomponents-client/pull/714#issuecomment-3227348839
@ok2c Hi, You are exactly right. However, my perspective is that when users employ the evictIdleConnections method, they do so based on the method name and its Javadoc, with the expectation of guaranteeing a maximum idle time for connections in the pool. This is often to proactively perform a client-side close, typically because they are aware of the server's idle timeout settings. Well, it becomes a matter of choice. With a 20s setting, some connections that have been idle for only 10s will indeed be evicted. This is a trade-off to ensure that the maximum idle time remains at 20s + execution time. This might be preferable to the current implementation where connections can potentially survive for up to 40s, which could violates the user's explicit configuration. The primary goal is to restrict maxIdleTime. However, if you feel I'm making too broad of an assumption about user expectations, please let me know and I will close this PR. Thank you. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
