mirrors/arti.git/crates/tor-circmgr/src/config.rs, branch arti-v0.0.4

Test for PathConfig::at_least_as_permissive_as().

2022-01-20T14:57:19Z

This is totally not just an exercise to get combined test coverage for tor-circmgr over 90% because I needed something to do that wouldn't distract anybody else. :)

Rename PathConfig::more_permissive_than()

2022-01-20T14:55:54Z

Since it implements a "<=" type relationship, it should be called "at_least_as_permissive_as()." Since it's a crate-private function, the long name isn't too bad.

Remove "self" arg from PathConfig::builder()

2022-01-20T14:53:12Z

This was added by mistake.

Adjust comment to be accurate wrt #263.

2021-12-16T13:37:50Z

Make preemptive circuits reconfigurable.

2021-12-07T21:42:58Z

This required re-centralizing the configuration object for preemptive circuits, since previously the settings from it were a bit spread out over the crate.

Make circuit_timing reconfigurable.

2021-12-07T21:08:52Z

Allow on-the-fly changing of path_rules

2021-12-07T20:42:14Z

And now the complexity begins: when the user changes the path_rules, they not only want new circuits to obey those rules: they want _all new requests_ to be put onto circuits that obey those rules. That means that when the path rules become more restrictive, we need to retire all the circuits, and make sure that currently pending circuits aren't used for any requests. If it's any comfort, doing this was even more complicated in C tor. ;)

Clarify names and docs for predictive circuits.

2021-12-07T17:09:05Z

Also, use humantime_serde, rather than a number of seconds, to indicate configuration time.

Rename circuits_preemptive to preemptive_circuits

2021-12-07T17:06:53Z

This obeys a few conventions: * adjective before noun * config objects end with "config"

Allow configurability on preemptive circuits

2021-12-07T15:04:41Z