Releases: ntex-rs/ntex-mqtt
ntex-mqtt v0.11.3
Changes
- Update BufferService usage
ntex-mqtt v0.11.0
Changes
- Release v0.11.0
ntex-mqtt v0.11.0 (beta.2)
Changes
- Use ContainerCall, remove unsafe
ntex-mqtt v0.11.0 (beta0)
- Migrate to ntex-0.7
ntex-mqtt v0.10.4
Changes
-
Expose size of prepared packet
-
Return packet and packet size from decoder
ntex-mqtt v0.10.3
Changes
-
Adds non-blocking qos1 publish sender
-
Adds validation of topic filters in SUBSCRIBE and UNSUBSCRIBE (#136)
ntex-mqtt v0.10.2
Changes
- Sink readiness depends on write back-pressure
ntex-mqtt v0.10.1
Changes
-
Fix missing ready wakes up from InFlightService
-
Register Dispatcher waker when service is not ready
ntex-mqtt v0.10.0
Changes
-
Change ConnectAck session_expiry_interval_secs type to Option
-
Introduce EncodeError::OverMaxPacketSize to differentiate failure to encode due to going over peer's Maximum packet size
ntex-mqtt v0.10.0-beta.2
Changes
-
Fix dispatcher leak during stop process
-
Refactor client error
-
Drop derive_more dep
-
Exposed QoS at crate's level, disbanded types module
-
Added v5::Sink::force_close()
-
Added v5::Client::into_inner()
-
packet properties with clear defaults per spec are represented without Option, use default when absent; for example, Session Expiry Interval, Maximum QoS, Retain Available, etc. in Connect and ConnectAck
-
server-level settings for Maximum QoS, Topic Alias Maximum and Receive Maximum are now applied at ConnectAck construction. Any changes to ConnectAck in Handshake service are honored on connection level.
-
Setting RETAIN on PUBLISH when CONNACK stated
Retain Available: 0
triggers Protocol Error -
Setting Subscription Identifier on SUBSCRIBE when CONNACK stated
Subscription Identifier Available: 0
triggers Protocol Error -
Topic name with
+
or#
in it will trigger Protocol Error -
Protocol violation errors are now grouped under opaque ProtocolViolationError
-
Removed Client re-export under v3 module. Use v3::client::Client instead.