swarm-wire: take agent_schedules's wire types
This commit is contained in:
parent
9cce9c470f
commit
e111807f59
1 changed files with 170 additions and 162 deletions
|
|
@ -7,11 +7,11 @@
|
|||
//! no swarm.
|
||||
//!
|
||||
//! **An agent reads with one `DIRECT.GET` on its own key, not a watch**, for
|
||||
//! the reason `swarm_queue_client::agent_schedules` gives: the direct get names the key
|
||||
//! in its subject ([`direct_get_subject`]), which is
|
||||
//! what lets the queue grant scope the read to one agent.
|
||||
//! the reason [`crate::agent_schedules`] gives: the direct get names the key
|
||||
//! in its subject ([`direct_get_subject`]), which is what lets the queue grant
|
||||
//! scope the read to one agent.
|
||||
//!
|
||||
//! Keyed by the agent alone, like `swarm_queue_client::agent_schedules`: an agent can
|
||||
//! Keyed by the agent alone, like [`crate::agent_schedules`]: an agent can
|
||||
//! move between hives.
|
||||
|
||||
/// The KV bucket inference settings are published into, keyed by agent name.
|
||||
|
|
|
|||
Loading…
Reference in a new issue