#[non_exhaustive]pub struct InMemoryMeshConfig {
pub emit_loopback_events: bool,
pub author_tag: Option<String>,
pub transport_name: String,
}Expand description
Configuration for InMemoryMeshRuntime behavior.
The defaults produce a minimal runtime suitable for unit testing.
Use InMemoryMeshConfig::loopback for a full-featured loopback
runtime that emits all mesh events (query, reply, topic).
§Event emission model
request() always emits a meshReply event (fix #129), regardless
of emit_loopback_events. When emit_loopback_events is true,
additional events are emitted: meshQuery on request(), meshReply
on respond(), and meshTopic on publish().
Private operations (request_private, publish_private_control,
publish_private_receipt) always emit their events when subscribed,
regardless of emit_loopback_events, because private mesh operations
are inherently interactive and omitting events would break the private
object handshake protocol.
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.emit_loopback_events: boolWhen true, request() additionally emits meshQuery events,
respond() emits meshReply, and publish() emits meshTopic
for active subscriptions.
Author tag attached to emitted events (e.g. Some("loopback")).
transport_name: StringTransport name returned by status().
Implementations§
Trait Implementations§
Source§impl Clone for InMemoryMeshConfig
impl Clone for InMemoryMeshConfig
Source§fn clone(&self) -> InMemoryMeshConfig
fn clone(&self) -> InMemoryMeshConfig
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more