Struct LegSetup 

pub(crate) struct LegSetup {
    pub(crate) client_installer: Option<Arc<dyn TransportInstaller>>,
    pub(crate) upstream_installer: Option<Arc<dyn TransportInstaller>>,
    pub(crate) upstream_webtransport: bool,
}

What the control plane knows about the two legs from the configuration the proxy was built with, and cannot learn any other way.

Copied out of the proxy’s templates when the plane is built rather than read back from them on demand, because a handle is reachable from tasks that do not hold the proxy.

Fields

client_installer: Option<Arc<dyn TransportInstaller>>

How a client-leg TransportProfile becomes the config the listener installs.

upstream_installer: Option<Arc<dyn TransportInstaller>>

The same for the relay leg.

upstream_webtransport: bool

Whether the relay leg is a WebTransport upstream, which cannot take transport parameters at all.

Implementations

impl LegSetup

fn from_config(config: &ProxyConfig) -> Self

What the control plane needs to know about the two legs, read off the configuration the proxy is being built with.

The installers are shared rather than copied, so a live TransportProfile is built by the same installer a configured one would have been.

Trait Implementations

impl Default for LegSetup

fn default() -> LegSetup

Returns the “default value” for a type.