Lines Matching +full:access +full:- +full:controllers

5 use of pluggable QUIC congestion controllers in the future. The interface is
14 Congestion controllers are not thread safe; the caller is responsible for
17 Congestion controllers may vary their state with respect to time. This is
19 `new` method, which provides access to a clock. While no current congestion
21 controllers to implement packet pacing.
23 Congestion controllers may expose arbitrary configuration parameters via the
24 `set_input_params` method. Equally, congestion controllers may expose diagnostic
28 to be common to all congestion controllers.
30 Currently, the only dependency injected to a congestion controller is access to
31 a clock. In the future it is likely that access at least to the statistics
35 congestion control algorithm requires access to the statistics manager, but such
36 access can readily be added later as needed.
38 QUIC congestion control state is per-path, per-connection. Currently we support
46 9002 pseudocode would require a congestion controller to access the ACK
54 controllers via a provider-based interface in the future.