ores.http.core
Table of Contents
Summary
ores.http.core implements the concrete HTTP route handlers for the ORE Studio
REST API. It registers routes for each domain: IAM (login, session), assets
(image serving), risk (report execution), storage, and variability
(configuration). Each route handler translates the incoming HTTP request into
NATS calls to the appropriate domain service and returns the NATS response as
an HTTP response.
Inputs
- Incoming HTTP requests dispatched from
ores.http.apirouter. - NATS responses from
ores.iam.service,ores.assets.service,ores.reporting.service, etc.
Outputs
- HTTP responses constructed from NATS domain service responses.
- Route registrations added to the
ores.http.apirouter and OpenAPI registry.
Entry points
include/ores.http.core/routes/iam_routes.hpp— IAM endpoint handlers.include/ores.http.core/routes/assets_routes.hpp— assets endpoint handlers.include/ores.http.core/routes/risk_routes.hpp— risk/reporting handlers.include/ores.http.core/routes/variability_routes.hpp— config handlers.include/ores.http.core/routes/storage_routes.hpp— storage handlers.
Dependencies
ores.http.api— server infrastructure, router, JWT claims.ores.iam.api,ores.assets.api,ores.reporting.api,ores.variability.api— NATS protocol types for each domain service called.nats.c— NATS client for forwarding requests.
See also
- ores.http.api — server infrastructure this library builds on.
- ores.http.server — server entrypoint that wires these routes.
