Enum Parsed 

pub enum Parsed {
    Complete {
        command: Command,
        consumed: usize,
    },
    Incomplete,
    Invalid {
        message: String,
        consumed: usize,
    },
    Fatal {
        message: String,
        too_large: bool,
    },
}

Result of trying to take one command off the front of a buffer.

Variants

Complete

A complete command, and how many bytes of the buffer it consumed.

Fields

command: Command

consumed: usize

Incomplete

Not enough bytes yet; leave the buffer alone and read more.

Invalid

The command line was well-framed but malformed. consumed bytes should still be dropped so the connection can continue.

For a storage command this includes its data block: rejecting the header while leaving <bytes> octets of attacker-chosen payload in the stream means those octets are then parsed as commands. See parse_storage.

Fields

message: String

consumed: usize

Fatal

The command line was malformed in a way that makes resynchronising impossible: the caller must reply and then close the connection.

This is only reachable from a storage command whose <bytes> count is missing, unparseable, or larger than MAX_VALUE_LEN. Every other malformed command is self-delimiting (one CRLF-terminated line), so the parser can skip it and carry on; a storage command whose length is unknown or unbufferable has no such boundary, and guessing one would put the peer’s payload back on the command path.

too_large separates the one fatal case that is a size refusal — a declared <bytes> over MAX_VALUE_LEN — from a length that is missing or not a number. The two get different replies: upstream memcached answers an oversized item with SERVER_ERROR object too large for cache, and a client keys its retry logic on that exact text.

Fields

message: String

too_large: bool

Trait Implementations

impl Debug for Parsed

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

Formats the value using the given formatter.