Skip to content

Abblix.SecurityEvents.Delivery Namespace

Classes
DeliveryErrorHow a receiver tells a transmitter that a SET was bad: the body of a push failure response (RFC 8935 Section 2.3) and the per-token value of a poll request's "setErrs" member (RFC 8936 Section 2.2), which share this shape by the latter's reference to the former.
DeliveryError.ParameterNamesThe wire names of the error members (RFC 8935 Section 2.3).
DeliveryErrorCodesThe IANA "Security Event Token Error Codes" registry's initial contents (RFC 8935 Section 2.4): the vocabulary a receiver reports a bad SET in. One registry serves both delivery methods - the push failure response uses it directly (RFC 8935 Section 2.3) and the poll protocol's per-token error reports reuse it by reference (RFC 8936 Section 2.6) - which is why the class is named for delivery rather than for push alone.
PollClientThe receiver's side of poll-based delivery (RFC 8936): one POST that acknowledges what was processed and asks for what waits. The wire shapes live beside it; this type owns only the transport.
PollDeliveryTransportThe HTTP transport a receiver polls a transmitter's pending tokens over (RFC 8936).
PollRequestThe body a SET Recipient posts to a transmitter's polling endpoint (RFC 8936 Section 2.2): what to return now, and what of the previous delivery is being acknowledged. The three request variations of Section 2.4 - poll-only, acknowledge-only, combined - are all spellings of this one object.
PollRequest.ParameterNamesThe wire names of the poll request members (RFC 8936 Section 2.2).
PollResponseThe body a SET Transmitter returns to a poll (RFC 8936 Section 2.3): the SETs being delivered, keyed by "jti" with each value the compact serialization, and whether more wait behind them.
PollResponse.ParameterNamesThe wire names of the poll response members (RFC 8936 Section 2.3).
PushDeliveryHandlerThe host-agnostic core of a push delivery endpoint (RFC 8935): one method from the raw transmission - content type and body - to the PushDeliveryResult the transport renders. A host adapter owns routing and transmitter authentication; this type owns everything the specifications say about the SET itself.
PushDeliveryResultWhat a push delivery request earns: the status code the transport answers with, and - only beside a 400 - the error body the transmitter reads (RFC 8935 Sections 2.2, 2.3). The shape is transport-neutral on purpose: any host adapter renders it, none decides it.
ReplayIdentifierComposes what a receiver reserves in IReplayCache for one token.
SecurityEventTokenMediaTypesThe media type a SET travels under (RFC 8417 Section 7.3). RFC 8935 Section 2.1 requires it as the Content-Type of a push transmission request; everything else in delivery - poll requests, poll responses, error bodies - is plain application/json, for which the framework's own constant serves.
Interfaces
ISecurityEventSinkWhere validated events land: the application's half of a receiver, called once per accepted SET with the token already carrying its issuer's authority.