Expand description
The production KeySender: a session’s keys delivered as a publish on
sessions.<id>.keys through the server’s own publish path (ACCESS-003
R1).
The keys are published only after Lys answered the deliberate ask
outright; a held act never reaches this sender. The publish goes through
ServicePublisher, whose real implementation is the connection
services’ embedded-host publish (publish_embedded): the same admission,
namespace refusal, durability and dedup a connection publish gets, with
publisher liminal.<host>. The request’s operation id is the
idempotency key, so a request sent again is delivered at most once. The
session’s runner subscribes to its own sessions.<id>.keys subject; a
subject the roster does not carry is refused by the roster, by name.
Structs§
- Channel
KeySender - Session keys published on
sessions.<id>.keys. - Connection
Publisher - The connection services’ embedded-host publish as a
ServicePublisher.
Constants§
- SESSION_
KEYS_ SCHEMA - The schema bytes the services’ messages are published under: the payload is the request’s bytes, unchanged, and the schema names which service carried them.
Traits§
- Service
Publisher - Publishes one service message on a subject, once per operation.
Functions§
- keys_
subject - The subject a session’s keys are delivered on.
- service_
envelope - The envelope one service message travels in.