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
http1_read_buf_exact_size, http1_max_buf_size, and http1_title_case_headers are all configuration methods on hyper::client::Builder, but not hyper::client::conn::Builder. I notice that the methods are present on the latter type but are pub(super) rather than pub.
Currently, I believe users of the conn interface are stuck with the default values of these settings. Are there any reasons not to make these pub with similar docstrings to the higher-level API? I'd be happy to provide a PR if not.
The text was updated successfully, but these errors were encountered:
I believe it is simply an oversight. I'd say more of the builder options also make sense on the conn types (besides pooling, listener config, the obvious).
client connection builders.
These options are currently available on the high-level builder only.
Along the way, rename the setters to follow the public API conventions
and add docs.
Closeshyperium#2461
…er` (#2611)
These options are currently available on the high-level builder only.
Along the way, rename the setters to follow the public API conventions
and add docs.
Closes#2461
http1_read_buf_exact_size
,http1_max_buf_size
, andhttp1_title_case_headers
are all configuration methods onhyper::client::Builder
, but nothyper::client::conn::Builder
. I notice that the methods are present on the latter type but arepub(super)
rather thanpub
.Currently, I believe users of the
conn
interface are stuck with the default values of these settings. Are there any reasons not to make thesepub
with similar docstrings to the higher-level API? I'd be happy to provide a PR if not.The text was updated successfully, but these errors were encountered: