Themis.Inference.Remote.Http 4.1.0

Themis.Inference.Remote.Http

Themis.Inference.Remote.Http provides a configurable HTTP transport for decision providers. The host supplies a protocol mapper that translates its wire contract into and out of Themis' typed decision requests. This shared module owns request/response dispatch, HTTP message lifetime, cancellation, status handling, and end-to-end latency measurement; protocol adapters own their wire schemas, validation, and answer semantics. It implements the existing IDecisionInferenceProvider without restricting applications that implement that interface directly with another transport.

Registration

Implement IRemoteDecisionHttpProtocol for the target service's request and response schema, then register it with the shared decision router:

using Themis.Core;
using Themis.Core.Extensions;
using Themis.Inference.Remote.Http;

services.AddThemisRemoteHttpDecisionInference<MyDecisionHttpProtocol>()
    .ConfigureHttpClient((serviceProvider, client) =>
    {
        client.BaseAddress = new Uri("https://inference.example/");
        client.Timeout = TimeSpan.FromSeconds(30);
    });
services.AddThemisDecisionRouter(new DecisionRouterOptions("model-v1")
{
    RouteUnspecifiedRequestsToDefaultModel = true
});

The protocol owns request and response mapping. HTTP status failures are raised as HttpRequestException, transport exceptions propagate unchanged, and cancellation is forwarded to both send and response processing. Configure authentication, retry/resilience, caching, and replay using the named HttpClient pipeline; policy, cache keys, TTL, and invalidation remain host-owned.

Service-specific remote packages should depend on this package and provide an IRemoteDecisionHttpProtocol adapter rather than maintaining a parallel IDecisionInferenceProvider HTTP lifecycle. Applications with a different transport or a custom HTTP implementation can still implement IDecisionInferenceProvider directly.

RPC findings

RPC is not implemented by this package. If a concrete RPC integration is approved, keep its client lifecycle, deadlines, metadata, retry behavior, and status/error mapping in a separate optional transport package. The existing IDecisionInferenceProvider remains the shared decision boundary; HTTP request and response mappers should not become an RPC abstraction. Avoid a separate transport-neutral remote core until a demonstrated shared implementation needs one.