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
MTU configuration is currently set on the builder for the tokio IO provider, meaning the configuration is the same across connections on an endpoint. There may be scenarios where finer-grained control of the MTU configuration is necessary,.
Solution:
Add mtu Configuration to the connection limits provider, so that each connection may receive a different MTU configuration.
Does this change what s2n-quic sends over the wire? Potentially changes the size of packets sent over the wire
Does this change any public APIs? --> Adds to the connection limit provider API
Requirements / Acceptance Criteria:
The user is able to configure MTU settings on the connection limit provider
The text was updated successfully, but these errors were encountered:
Problem:
MTU configuration is currently set on the builder for the tokio IO provider, meaning the configuration is the same across connections on an endpoint. There may be scenarios where finer-grained control of the MTU configuration is necessary,.
Solution:
Add mtu Configuration to the connection limits provider, so that each connection may receive a different MTU configuration.
Requirements / Acceptance Criteria:
The user is able to configure MTU settings on the connection limit provider
The text was updated successfully, but these errors were encountered: