Selva Compute API Reference - v2.1.0
    Preparing search index...

    Interface SolveSchedulerOptions

    interface SolveSchedulerOptions {
        cache?: boolean | CacheOptions;
        maxConcurrent?: number;
        mode?: SchedulerMode;
        onSettle?: (ctx: SolveContext, result: SolveResult) => void;
        onStart?: (ctx: SolveContext) => void;
        onSuperseded?: (ctx: SolveContext) => void;
        retry?: RetryPolicy;
        reuseServerDefinitionCache?: boolean;
        timeoutMs?: number;
    }
    Index

    Properties

    cache? maxConcurrent? mode? onSettle? onStart? onSuperseded? retry? reuseServerDefinitionCache? timeoutMs?

    Properties

    cache?: boolean | CacheOptions

    Enable response caching keyed by hash of (definition, dataTree).

    maxConcurrent?: number
    mode?: SchedulerMode
    onSettle?: (ctx: SolveContext, result: SolveResult) => void
    onStart?: (ctx: SolveContext) => void

    Lifecycle hooks — fired in order. Errors thrown by hooks are logged, not rethrown.

    onSuperseded?: (ctx: SolveContext) => void
    retry?: RetryPolicy
    reuseServerDefinitionCache?: boolean

    Reuse the server's definition cache key so a large (base64/binary) definition is uploaded once and subsequent solves reference it by pointer instead of re-sending the full payload. Hugely cheaper for multi-MB definitions on a live UI (slider scrubs, etc.).

    Requires a cacheKeyExecutor to be supplied (the client wires one). Has no effect for URL-pointer definitions (already a reference). On a server-side cache miss the executor transparently falls back to a full upload, so this is safe to leave on. Default: true when a cacheKeyExecutor is present.

    timeoutMs?: number

    Settings

    Member Visibility

    On This Page

    Properties