docs(#3255): the announce doc described the design the rework replaced
The function's own doc comment still said one subject per hive, four lines above an inline comment correctly saying one publish for all of them. Left behind by the single-writer rework. Swept the rest of the touched files for the old design's vocabulary rather than fixing only the line argus quoted: every other per-hive mention is about webhook registration or the callout policy's extra-subject template, both of which are still per-hive and still accurate.
This commit is contained in:
parent
33958d78ae
commit
3c390f8132
1 changed files with 3 additions and 3 deletions
|
|
@ -388,9 +388,9 @@ pub(super) async fn post_webhook_forge(
|
||||||
/// everything from the repository itself. So what crosses the queue is an edge
|
/// everything from the repository itself. So what crosses the queue is an edge
|
||||||
/// trigger, and adding fields to it would invent a contract nobody reads.
|
/// trigger, and adding fields to it would invent a contract nobody reads.
|
||||||
///
|
///
|
||||||
/// One subject per hive rather than one shared subject, so the swarm's callout
|
/// One publish to one shared subject, not one per hive: every subscriber gets
|
||||||
/// policy can express "this hive may hear its own events" at all; a subject
|
/// the same empty event, so the roster is never consulted and this daemon does
|
||||||
/// with no hive component is the same subject for everyone.
|
/// not need to know who the hives are in order to tell them.
|
||||||
///
|
///
|
||||||
/// # Failure
|
/// # Failure
|
||||||
///
|
///
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue