Skip to main content

Module message

Module message 

Source
Expand description

What a tap carries: the filter, the grant, the publish it is shown, and the per-message facts it keeps.

Structs§

CallDetails
Terminal call fields the console can read without a payload grant.
CallFact
One call as seen at its terminal correlation or deadline.
Hop
One point a message crossed: the node, shared rather than copied, and how long after the message was first seen.
PayloadGrant
The right to see payloads on a tap. Nothing in the server mints one until grants (SRV-011 R4) exist, so no payload leaves through a tap today.
PublishFact
One publish as the hook hands it to the tap. Borrowed throughout: the tap copies only what an admitted message keeps.
Reached
A station a message reached: its id, shared rather than copied, and the instant the first of its subscriptions’ inboxes queued the message.
Recorded
What a recording publish saw, all together, so a fact can never carry recipients’ queue instants without the receipt they are measured from (Hermes 7 Oct 06:55).
TapBatch
What a drain hands the subscriber: messages that were all admitted at one divisor.
TapFilter
Which messages a subscription wants: those whose subject (the channel name) equals subject, or starts with its prefix when it ends in *. An empty subject or a lone * matches everything.
TapMessage
The per-message facts a tap keeps.

Enums§

TapIdent
How a tapped message is named: by the server’s message id when it was admitted, by the tap’s observation number when it was not.
TapOutcome
What became of a tapped publish, by the cause the server knows. A dedup-suppressed re-publish is never tapped: its original was.
TapSource
Who published.