Skip to main content

Module spec

Module spec 

Source
Expand description

The OperationSpec registry: every fact about an operation, declared once.

v2 scattered these facts across 10+ match sites and five parallel billable lists; here classification, settlement, affinity, and console metadata all read one declaration. Request-body expectations are not a field — they derive from the ingress method (single truth).

Structs§

Ingress
One way this operation enters the proxy.
Matched
A successful ingress match.
OperationSpec
Everything the engine needs to know about an operation.
PathPattern

Enums§

Affinity
Which credential-stickiness the operation needs.
Seg
One path segment of an ingress pattern. Static tables, no matcher DSL: the full pattern language is exactly what the known APIs need.
SettleMode
When the funnel settles this operation.
StreamDetect
How to tell a streaming request from a buffered one at this ingress.
StreamFraming

Functions§

default_framing
streaming_sibling
Streaming promotion: which operation a BodyFlag ingress becomes when the flag is set. Exhaustive so a new streaming pair cannot be missed.