Skip to content

fork-safety.md

Latest commit

 

History

History
44 lines (30 loc) · 1.36 KB

fork-safety.md

File metadata and controls

44 lines (30 loc) · 1.36 KB

Fork Safety

HTTPKernel is built around a strict parent/request ownership split.

Parent-Safe State

The long-lived kernel object is intended to keep only structural and immutable state such as:

  • adapter wiring
  • exchange factory wiring
  • lifecycle event coordinator wiring
  • execution boundary wiring
  • runtime context factory configuration
  • handler boundary wiring
  • failure mapping wiring
  • response finalizer wiring
  • emitter boundary wiring

Request-Owned State

The following objects are request-owned and must not remain in warmed parent state:

  • HttpRequestInterface
  • RequestBodyInterface
  • HttpExchangeInterface
  • HttpResponseInterface
  • request RuntimeContext
  • request ScopeId

Implemented Safety Checks

The current test suite verifies that:

  • HttpKernel does not retain request, body, exchange, or response objects on persistent properties after handling
  • each request gets a fresh runtime context and scope id
  • handler execution happens behind the execution boundary using child-side runtime scope data

Current Execution Model

HTTPKernel delegates execution to MicroKernel.

It does not call raw POSIX or PCNTL process-control functions directly.

The current package tests prove the package boundary and object-retention rules through the MicroKernel execution API. They do not claim more than the current upstream execution surface provides.