Repository navigation
Release v1.9.0
Ante can now address a lobby's host-store traffic by audience, so a lobby only receives the invitations meant for it and its replies go back to the operator that asked.
Added
Ante:Audience(Ante__Audience) names the lobby. When set, every host-store subscription is filtered to that audience; when unset or empty, subscriptions stay unfiltered as before.Ante:OperatorAudienceis the fallback reply audience when a request does not say who sent it. When unset, replies stay unaddressed as before.Ante.Contracts.AudienceTags.From("from") is the tag a host sets to name the requesting operator; replies to that request are addressed to it. No event schema changes.- Startup validation rejects blank or padded audience values with
AnteAudienceInvalid. - Documentation for audience routing in the configuration and host-integration guides: https://github.com/Cratis/Ante/blob/main/Documentation/host-integration.md
Changed
- Receipts, revocations, reservations and the other replies a lobby publishes to the host outbox are addressed to the operator that sent the originating request. Requests carrying no
fromfall back toAnte:OperatorAudience, then to unaddressed.