Releases: minghuaw/fe2o3-amqp
Releases · minghuaw/fe2o3-amqp
v0.7.0
0.7.0
- Changed message body to a trait, and thus supporting more than one
Data
orAmqpSequence
sections. Please see 0.7.0 migration guide for more details. - Logging with
tracing
orlog
is now toggled by enabling the corresponding feature flag
v0.6.8
Quality of life update
-
Connection::open()
andconnection::Builder::open()
now are able to take an actualurl::Url
instance as argument, meaning the code below will work now.let url = url::Url::parse("amqp://localhost:5671").unwrap() let connection = Connection::open("container_id", url).await.unwrap();
let url = url::Url::parse("amqp://localhost:5671").unwrap() let connection = Connection::builder() .container_id("container_id"), .open(url).await.unwrap();
v0.6.7
0.6.7
- Disposition of message (
accept()
,reject()
,release()
,modify()
,accept_all()
,reject_all()
,release_all()
,modify_all()
) on the receiver side no longer requires&mut self
. They only need&self
now. - Allow receiver disposition methods (
accept()
,reject()
,release()
,modify()
,accept_all()
,reject_all()
,release_all()
,modify_all()
) to take any type that implementInto<DeliveryInfo>
. This includes bothDelivery<T>
and&Delivery<T>
- Switched internal
RwLock
fromtokio::sync::RwLock
toparking_lot::RwLock
to resolve cancel safety issue withReceiver::recv()
#22- Switching from an async
RwLock
to a blockingRwLock
is fine because the lock guard will never be held across.await
points.
- Switching from an async
v0.6.3
v0.6.2
v0.6.1
v0.5.1
v0.4.2
v0.4.1
v0.4.0
What's Changed
- 78 add symbol ref by @minghuaw in #80
- 83 rework connection and session local errors by @minghuaw in #85
- Breaking changes:
- Restructured
connection::error::{OpenError, Error}
andsession::error:{BeginError, Error}
DecodeError
variant now carries aString
message of theserde_amqp::Error
- Restructured
Connection
and non-txnSession
no longer hold a copy of the controller sender to its own engine- Resuming receiver now doesn't assume the continued payload transfer starts at the receiver's
Received
state - Made
Sendable
's fields public - Renamed
role::Sender/Receiver
torole::SenderMarker/ReceiverMarker
to avoid confusion - Updated documentations on
Sender::send
Sender::attach
Receiver::attach
Full Changelog: v0.3.0...v0.4.0