pub struct CircMgr<R: Runtime> { /* fields omitted */ }
Expand description

A Circuit Manager (CircMgr) manages a set of circuits, returning them when they’re suitable, and launching them if they don’t already exist.

Right now, its notion of “suitable” is quite rudimentary: it just believes in two kinds of circuits: Exit circuits, and directory circuits. Exit circuits are ones that were created to connect to a set of ports; directory circuits were made to talk to directory caches.

Implementations

Construct a new circuit manager.

Try to change our configuration settings to new_config.

The actual behavior here will depend on the value of how.

Reload state from the state manager.

We only call this method if we don’t have the lock on the state files. If we have the lock, we only want to save.

Switch from having an unowned persistent state to having an owned one.

Requires that we hold the lock on the state files.

Flush state to the state manager, if there is any unsaved state and we have the lock.

Reconfigure this circuit manager using the latest set of network parameters.

(NOTE: for now, this only affects circuit timeout estimation.)

Return true if netdir has enough information to be used for this circuit manager.

(This will check whether the netdir is missing any primary guard microdescriptors)

Reconfigure this circuit manager using the latest network directory.

This should be called on any change to the network, as opposed to CircMgr::update_network_parameters, which should only be called when the parameters change.

Return a circuit suitable for sending one-hop BEGINDIR streams, launching it if necessary.

Return a circuit suitable for exiting to all of the provided ports, launching it if necessary.

If the list of ports is empty, then the chosen circuit will still end at some exit.

Launch circuits preemptively, using the preemptive circuit predictor’s predictions.

Note

This function is invoked periodically from the arti-client crate, based on timings from the network parameters. As with launch_timeout_testing_circuit_if_appropriate, this should ideally be refactored to be internal to this crate, and not be a public API here.

If circ_id is the unique identifier for a circuit that we’re keeping track of, don’t give it out for any future requests.

If we need to launch a testing circuit to judge our circuit build timeouts timeouts, do so.

Note

This function is invoked periodically from the arti-client crate, based on timings from the network parameters. Please don’t invoke it on your own; I hope we can have this API go away in the future.

I would much prefer to have this not be a public API, and instead have it be a daemon task. The trouble is that it needs to get a NetDir as input, and that isn’t possible with the current CircMgr design. See arti#161.

Trait Implementations

Returns a copy of the value. Read more

Performs copy-assignment from source. Read more

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more

Immutably borrows from an owned value. Read more

Mutably borrows from an owned value. Read more

Performs the conversion.

Instruments this type with the provided Span, returning an Instrumented wrapper. Read more

Instruments this type with the current Span, returning an Instrumented wrapper. Read more

Performs the conversion.

Should always be Self

The resulting type after obtaining ownership.

Creates owned data from borrowed data, usually by cloning. Read more

🔬 This is a nightly-only experimental API. (toowned_clone_into)

Uses borrowed data to replace owned data, usually by cloning. Read more

The type returned in the event of a conversion error.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.

Attaches the provided Subscriber to this type, returning a WithDispatch wrapper. Read more

Attaches the current default Subscriber to this type, returning a WithDispatch wrapper. Read more