ConfiguredStream Class
One stream as a closed deployment declares it: the shape a first-party transmitter binds from configuration when its receivers are its own products, known at deploy time and provisioned by the same operator on both sides. The members are deliberately binder-friendly - strings, arrays, a URL - so the whole stream set can live in the host's configuration.
public sealed record ConfiguredStream : System.IEquatable<Abblix.SharedSignals.Transmitter.ConfiguredStream>Inheritance System.Object → ConfiguredStream
Implements System.IEquatable<ConfiguredStream>
Properties
ConfiguredStream.Audiences Property
The "aud" of the stream's SETs; empty uses the receiver identity itself, the default the dynamic path also takes (SSF 1.0 Section 4.1.8).
public string[] Audiences { get; init; }Property Value
ConfiguredStream.Description Property
A human-readable description of the stream (SSF 1.0 Section 8.1.1).
public string? Description { get; init; }Property Value
ConfiguredStream.EventsRequested Property
The event types the receiver wants; what the stream carries is the intersection with the transmitter's supported set (SSF 1.0 Section 8.1.1).
public string[] EventsRequested { get; init; }Property Value
ConfiguredStream.PushAuthorizationHeader Property
The whole Authorization header line the transmitter sends with every push (SSF 1.0 Section 6.1.1). A secret: in a deployment it arrives through the host's secret mechanism - an environment variable mounted from a secret store - never as plaintext in a settings file.
public string? PushAuthorizationHeader { get; init; }Property Value
ConfiguredStream.PushEndpointUrl Property
The receiver's push endpoint; set makes the stream push-delivered, absent makes it poll over the transmitter's own endpoint (SSF 1.0 Section 6.1).
public System.Uri? PushEndpointUrl { get; init; }Property Value
ConfiguredStream.ReceiverId Property
The receiver identity the stream belongs to, matching what the host's authentication yields for that receiver's management and poll calls.
public string ReceiverId { get; init; }Property Value
Remarks
required binds the host that writes these in code and nothing else: the
configuration binder does not honour it, so a settings file omitting this member produces
null here without complaint. The guarantee is restored where the declarations are read -
ConfigurationStreamStore refuses a stream missing either identifier - and the
marker is kept because it still catches the code-first half at compile time.
ConfiguredStream.StreamId Property
The stream's identifier. Fixed by configuration rather than generated, so both sides of a first-party pair can name it in their own settings.
public string StreamId { get; init; }Property Value
ConfiguredStream.SubjectsMode Property
Which subjects the stream covers. The default here is All, the opposite of the dynamic path's conservative NONE - a first-party receiver is provisioned to hear everything, and per-subject bookkeeping is exactly what a static deployment does without.
public Abblix.SharedSignals.Transmitter.StreamSubjectsMode SubjectsMode { get; init; }