Module registry 

The study registry as the phases and the manual actions see it: what can be asked of it, in the pipeline’s terms. Request ids, wire items, the limiter, the breakers and audit bodies are the adapter’s; splitting a refused batch is the batch runner’s.

Re-exports

pub use answers::PersonLookupError;

pub use answers::RegistryPerson;

Modules

answers 🔒

What the study registry answered for one item, read into the pipeline’s terms.

batch 🔒

One batch request to the study registry and what came of it, row by row.

ids 🔒

The identifiers the study registry’s requests and answers carry.

requests 🔒

What one item of a request to the study registry asks.

Structs

RegistryError 🔒

A study registry request that failed as a whole: a value the rows’ outcomes are decided from, not an error of the iteration.

Enums

RegistryOperation 🔒

What the pipeline asks of the study registry, one variant per kind of request. The Suotar adapter maps each to its endpoint.

Traits

InteractiveStudyRegistry 🔒

The study registry for someone waiting on the answer: no allowance, and no breaker learns from its calls, so one click cannot trip the workers’. Not StudyRegistry, whose calls go through the iteration’s gate.

StudyRegistry 🔒

The study registry a phase iteration asks, through its limiter and breakers. The seam a use-case test would fake; only the Suotar adapter implements it. Generic rather than dyn.