#[non_exhaustive]pub struct SendOptions {
pub id: Option<String>,
pub ttl: Option<Duration>,
pub requires: Vec<String>,
pub correlation_id: Option<String>,
pub priority: Option<u8>,
pub live: bool,
}Expand description
How a message goes (Client::send_with).
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.id: Option<String>Its id: the application’s own (one it keeps in its own outbox, say), or a random UUID. The outcome events name it.
ttl: Option<Duration>How long it may wait before it is first sent: past it, it is dropped
and the application told (Event::NotDelivered,
expired). Once written it waits for the server’s answer whatever
its age. None: the outbox’s max_age.
requires: Vec<String>Topics that must each be continuous when it goes (see
Client::send_requiring).
correlation_id: Option<String>The id the application’s reply names (cid): its request and its
response.
priority: Option<u8>How urgent the application says it is (pri; the other clients
name 10 critical, 8 high, 5 normal, 3 low, 1 background). It is for
the server’s application: the outbox keeps the order messages were
sent in.
live: boolOn the connection that is ready now, or not at all, as
Client::try_send_live: never kept in the outbox. It waits for
nothing, so it takes no ttl and requires no topics.