Enum rml_rtmp::sessions::ClientSessionErrorKind

pub enum ClientSessionErrorKind {
    ChunkDeserializationError(ChunkDeserializationError),
    ChunkSerializationError(ChunkSerializationError),
    MessageSerializationError(MessageSerializationError),
    MessageDeserializationError(MessageDeserializationError),
    CantConnectWhileAlreadyConnected,
    SessionInInvalidState {
        current_state: ClientState,
    },
    NoKnownActiveStreamIdWhenRequired,
    CreateStreamFailed,
    CreateStreamResponseHadNoStreamNumber,
    InvalidOnStatusArguments,
}

Represents the type of error that occurred

Variants

ChunkDeserializationError(ChunkDeserializationError)

Encountered when an error occurs while deserializing the incoming byte data

ChunkSerializationError(ChunkSerializationError)

Encountered when an error occurs while serializing outbound messages

MessageSerializationError(MessageSerializationError)

Encountered when an error occurs while turning an RTMP message into an message payload

MessageDeserializationError(MessageDeserializationError)

Encountered when an error occurs while turning a message payload into an RTMP message

CantConnectWhileAlreadyConnected

Encountered if a connection request is made while we are already connected

SessionInInvalidState

Encountered if a request is made, or a response is received for a request while the client session is not in a valid state for that purpose.

Fields of SessionInInvalidState

current_state: ClientState

NoKnownActiveStreamIdWhenRequired

Encountered when attempting to send a message that requires having an active stream opened but none is marked down. This is almost always a bug with the ClientSession as this means we are in a valid state (e.g. Playing or Publishing) yet we never recorded what stream id we are publishing/playing on.

CreateStreamFailed

Encountered when the client requests a stream be created and the server rejects the command

CreateStreamResponseHadNoStreamNumber

A response to a createStream request should have a numeric as the first parameter in the additional values property of the amf0 command. This error is thrown if this is not present. Without a stream ID we have no way to know what stream to communicate with for playback/publishing messages.

InvalidOnStatusArguments

When the server sends and onStatus message, it is expected that the additional arguments contains a single value representing an amf0 object. This is required because the object should have a code property that says the type of operation the status is for.

Trait Implementations

impl Debug for ClientSessionErrorKind

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

Formats the value using the given formatter.

impl Display for ClientSessionErrorKind

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

Formats the value using the given formatter.

impl Fail for ClientSessionErrorKind

fn name(&self) -> Option<&str>

Returns the "name" of the error.

fn cause(&self) -> Option<&dyn Fail>

Returns a reference to the underlying cause of this failure, if it is an error that wraps other errors.

fn backtrace(&self) -> Option<&Backtrace>

Returns a reference to the Backtrace carried by this failure, if it carries one.

fn context<D>(self, context: D) -> Context<D> where     D: Display + Send + Sync + 'static,

Provides context for this failure.

fn compat(self) -> Compat<Self>

Wraps this failure in a compatibility wrapper that implements std::error::Error.