Enum RequestBody 

pub enum RequestBody {
    Hello {
        version: u32,
        settings: Option<Settings>,
    },
    Step {
        step: Step,
    },
    Relocate,
    Bye,
}

What the client wants done.

do names either a control message or a step, using the same vocabulary as flow files and chained argv — so {"do":"click"} is the wire form of action = "click". Because one key names both kinds, the two are separated by hand in parse_request rather than by a derive; the payoff is that a client writes the verb it already knows instead of nesting it under a wrapper.

Variants

Hello

First message: agree on a version before anything else happens, and optionally set the run settings for the whole session — the same fields a flow file’s [settings] table carries, so there is nothing new to learn and no CLI flag to keep in sync.

Fields

version: u32

settings: Option<Settings>

Step

Perform one step.

Fields

step: Step

Relocate

Re-locate every region and report where they are, without acting.

Bye

End the session. Closing stdin does the same thing.

Trait Implementations

impl Clone for RequestBody

fn clone(&self) -> RequestBody

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for RequestBody

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

Formats the value using the given formatter.

impl PartialEq for RequestBody

fn eq(&self, other: &RequestBody) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for RequestBody