Skip to content

runtime-scope.md

Latest commit

 

History

History
51 lines (30 loc) · 1.31 KB

runtime-scope.md

File metadata and controls

51 lines (30 loc) · 1.31 KB

Runtime Scope

HTTPKernel creates request runtime scope data after entering the execution boundary.

Runtime Context Factory

The package currently ships:

  • LiquidRazor\HttpKernel\Lib\Runtime\HttpRuntimeContextFactory

It creates:

  • one ScopeId per request
  • one RuntimeContext per request

The factory keeps only immutable configuration:

  • active Environment
  • scope id prefix

It does not retain generated request contexts or scope ids.

Scope Rules

Implemented behavior:

  • every request gets a new scope id
  • different requests get different scope ids
  • the runtime context carries the active environment
  • runtime parameters are normalized to a deterministic string-keyed shape when used

Execution Boundary Behavior

When HTTP work enters MicroKernel, the runtime scope seen by the handler is the child-side scope produced by MicroKernel.

That runtime context currently contains:

  • the request scope id
  • work_name
  • worker_id

Current Limitation

The current MicroKernel public execution API does not accept caller-supplied runtime parameters for HTTP execution.

Because of that:

  • HTTPKernel can supply the request scope id
  • HTTPKernel cannot inject arbitrary request runtime parameters into MicroKernel execution yet

This limitation is enforced explicitly rather than hidden behind local overrides.