Struct CheckoutOptions 

#[non_exhaustive]
pub struct CheckoutOptions {
    pub connect_headers: Vec<(String, String)>,
}

Host-side context for one checkout, as opposed to the ReplConfig the worker is sent.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

connect_headers: Vec<(String, String)>

Extra headers for this checkout’s WebSocket upgrade request; the subprocess transport makes no request and ignores them. Duplicate names are last-wins, even against the default user-agent (monty-pool/<version>), the traceparent from telemetry, host and the other handshake headers, and a malformed name or value fails the dial.

Implementations

impl CheckoutOptions

pub fn with_connect_headers( self, connect_headers: Vec<(String, String)>, ) -> Self

Sets the headers for this checkout’s WebSocket upgrade request.

Trait Implementations

impl Debug for CheckoutOptions

Names each connect header, never its value: monty never interprets the values, but a caller may send e.g. a token for a proxy/relay in front of the worker, and options get logged.

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for CheckoutOptions

fn default() -> Self

Returns the “default value” for a type.