Enum sage_mqtt::ReasonCode [−][src]
pub enum ReasonCode {
Show 43 variants
Success,
GrantedQoS1,
GrantedQoS2,
DisconnectWithWillMessage,
NoMatchingSubscribers,
NoSubscriptionExisted,
ContinueAuthentication,
ReAuthenticate,
UnspecifiedError,
MalformedPacket,
ProtocolError,
ImplementationSpecificError,
UnsupportedProtocolVersion,
ClientIdentifierNotValid,
BadUserNameOrPassword,
NotAuthorized,
ServerUnavailable,
ServerBusy,
Banned,
ServerShuttingDown,
BadAuthenticationMethod,
KeepAliveTimeout,
SessionTakenOver,
TopicFilterInvalid,
TopicNameInvalid,
PacketIdentifierInUse,
PacketIdentifierNotFound,
ReceiveMaximumExceeded,
TopicAliasInvalid,
PacketTooLarge,
MessageRateTooHigh,
QuotaExceeded,
AdministrativeAction,
PayloadFormatInvalid,
RetainNotSupported,
QoSNotSupported,
UseAnotherServer,
ServerMoved,
SharedSubscriptionsNotSupported,
ConnectionRateExceeded,
MaximumConnectTime,
SubscriptionIdentifiersNotSupported,
WildcardSubscriptionsNotSupported,
}
Expand description
A ReasonCode
is an identifier describing a response in any ackowledgement
packet (such as Connack
or SubAck
)
Variants
Generic success reason code indicating an operation performed well. According to the emmiting packet, the following meanings are applied:
Disconnect
: Normal DisconnectionSubAck
: Granted QoS 0
The subscription is accepted and the maximum QoS sent will be QoS 1.
The subscription is accepted and any received QoS will be sent..
The client disconnects but want the last will to be sent anyways.
The message is accepted but there are no subscribers.
No matching topic filter is being used by the client
Continue de authentication with another step
Initiate re-Authentication
The server doesn’t want or cannot describe the error
The control packet cannot be parsed or is ill-formed
The control packet is well formed but invalid according to specifications.
The operation is valid but not accepted by, the server
The requested MQTT version is not supported
The client identifier is not valid
The server does not accept the given user name or password
The operation is not permitted
The server is not available
The server is busy
The client is banned
The server is currently shutting down
The authentication method is not supported by the server
The connection is closed because not packet has been received for 1.5 times the keep alive period.
Another connection using the same client id has connected, causing this connection to be closed.
The topic filter is correctly formed but not accepted by the server.
The topic name is correctly formed but not accepted by the server
The packet identifier is already in use. This might indicate a mismatch in the session state between the client and the server.
The Packet Identifier is not known. This is not an error during recovery, but at other times indicates a mismatch between the Session State on the Client and Server.
The Client or Server has received more than receive maximum.
The topic alias is invalid
The packet size is greater than the maximum packet size fo rthis client or server.
The received data is too high
An implementation or administrative limite has been exceeded
The connection is closed due to an administrative action
The payload format does not match the one indicated in the payload format indicator.
The server does not support retain messages
The client specified a QoS greater than the maximum indicated in the
Connack
packet.
The client should temporarily change its server.
The client should permanently change its server.
The server does not support shared subscriptions
The connection is closed because the connection rate is too high
The maximum connect time authorized for this connection has exceeded.
The server does no support subscription identifiers.
The server does not support wildcard subcriptions.
Trait Implementations
Performs the conversion.
Auto Trait Implementations
impl RefUnwindSafe for ReasonCode
impl Send for ReasonCode
impl Sync for ReasonCode
impl Unpin for ReasonCode
impl UnwindSafe for ReasonCode
Blanket Implementations
Mutably borrows from an owned value. Read more