You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey,
I was trying to understand the flow of Do function and noticed that all idle connections are being closed if we are not able to read the request body or if all retries are exhausted and we still have an error.
Can't we selectively close the current connection that is causing problems rather than closing all the good connections that can be reused for subsequent requests to the same host.
I am trying to understand the reasoning behind this as we are going to integrate this lib in production service with a high throughput and I am uncomfortable with the impact of closing idle connections.
TIA for helping me out.
The text was updated successfully, but these errors were encountered:
Hey,
I was trying to understand the flow of
Do
function and noticed that all idle connections are being closed if we are not able to read the request body or if all retries are exhausted and we still have an error.Can't we selectively close the current connection that is causing problems rather than closing all the good connections that can be reused for subsequent requests to the same host.
I am trying to understand the reasoning behind this as we are going to integrate this lib in production service with a high throughput and I am uncomfortable with the impact of closing idle connections.
TIA for helping me out.
The text was updated successfully, but these errors were encountered: