Skip to content

Conversation

@vinzmyko
Copy link
Contributor

@vinzmyko vinzmyko commented Nov 1, 2025

Addresses #2500

Added documentation to clarify the current behavior and limitations.

Changes:

  • Added Connection Pooling section to Client struct explaining defaults and current limitations
  • Updated pool_idle_timeout() and pool_max_idle_per_host() docs to clarify they only affect idle connections

Happy to adjust based on feedback!

Add connection pooling section to Client struct docs and update
pool_idle_timeout and pool_max_idle_per_host methods.
Copy link
Owner

@seanmonstar seanmonstar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking the time to improve the docs!

I reminded myself what that issue said, and yea, I'd be happy with adding a sub section to the struct docs. I suspect that is sufficient...

/// # Connection Pooling
///
/// The Client maintains a pool of reusable HTTP connections to avoid
/// connection setup overhead.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a sentence a few lines up saying similar. What if we took the essence of that line ("holds a connection pool internally"), and merged it with this one?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point! Merged them to avoid redundancy.

@vinzmyko
Copy link
Contributor Author

vinzmyko commented Nov 4, 2025

Thanks for the feedback! I've addressed all your comments.

@seanmonstar seanmonstar merged commit a97e195 into seanmonstar:master Nov 4, 2025
37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants