Skip to main content

MobScopeResolver

meerkat_mobkit::memory::coordinator

Trait MobScopeResolver 

Source 
pub trait MobScopeResolver: Send + Sync {
    // Required method
    fn active_mobs(&self, realm: &str, identity: &str) -> Vec<String>;
}
Expand description

§7.2 identity→mob binding seam, mirroring OperatorResolver. The hosting runtime knows which mob(s) an identity serves (the same source that pins MemoryRecorder::mob for propose_to_mob); this trait keeps the coordinator free of roster coupling. Without a resolver installed — or when it yields no mobs — composition is unchanged, so mob-scope reads activate exactly when a binding exists.

Required Methods§

Source

fn active_mobs(&self, realm: &str, identity: &str) -> Vec<String>

The mobs identity is currently bound to in realm (§7.2 “Mob (bound mobs)” — plural). Empty means no mob scope joins composition.

Dyn Compatibility§

This trait is dyn compatible.

In older versions of Rust, dyn compatibility was called "object safety".

Implementors§